Dynamic location monitoring for targeted updates

ABSTRACT

In one embodiment, a technique including receiving, from a client system of a user, a first location of the client system. The technique further including receiving, from the client system, an ID of an access point detected by the client system. The technique also including accessing, by the one or more computing devices, an index to determine a second location of the access point based on the ID. The technique further including determining, by the one or more computing devices, a refined location of the client system based on the first location and the second location. The technique also including generating, by the one or more computing devices, a prioritized list of regions based on the refined location and user data. The technique further including transmitting, by the one or more computing devices, information associated with the prioritized list of regions to the client system.

TECHNICAL FIELD

This disclosure generally relates to location-related social networking.

BACKGROUND

A social-networking system, which may include a social-networking website, may enable its users (such as persons or organizations) to interact with it and with each other through it. The social-networking system may, with input from a user, create and store in the social-networking system a user profile associated with the user. The user profile may include demographic information, communication-channel information, and information on personal interests of the user. The social-networking system may also, with input from a user, create and store a record of relationships of the user with other users of the social-networking system, as well as provide services (e.g., wall posts, photo-sharing, event organization, messaging, games, or advertisements) to facilitate social interaction between or among users.

The social-networking system may send over one or more networks content or messages related to its services to a mobile or other computing device of a user. A user may also install software applications on a mobile or other computing device of the user for accessing a user profile of the user and other data within the social-networking system. The social-networking system may generate a personalized set of content objects to display to a user, such as a newsfeed of aggregated stories of other users connected to the user.

A mobile computing device—such as a smartphone, tablet computer, or laptop computer—may include functionality for determining its location, direction, or orientation, such as a GPS receiver, compass, gyroscope, or accelerometer. Such a device may also include functionality for wireless communication, such as BLUETOOTH communication, near-field communication (NFC), or infrared (IR) communication or communication with a wireless local area networks (WLANs) or cellular-telephone network. Such a device may also include one or more cameras, scanners, touchscreens, microphones, or speakers. Mobile computing devices may also execute software applications, such as games, web browsers, or social-networking applications. With social-networking applications, users may connect, communicate, and share information with other users in their social networks.

SUMMARY OF PARTICULAR EMBODIMENTS

The disclosure relates to a technique for determining a location of a client system by using access points. This technique may be useful when global positioning service (GPS) geolocation is unavailable or inaccurate. In particular, a client system is configured to detect broadcasted signals from one or more access points. A localization application executed by the client system, a social-networking system, a cloud computing system, and/or a third-party server further determines a location of each detected access point and triangulates the location of the client device based on the access point locations. The localization application further generates a set of prioritized regions. A region may be denoted a prioritized region based on a user's affinity for one or more target destinations included in the region and the proximity of the region to the triangulated location of the client system. The localization application further generates and outputs location updates corresponding to at least one prioritized region. The location update may include information about a target destination included in the prioritized region, directions to the target destination, an advertisement associated with the target destination, and so forth.

The embodiments disclosed herein are only examples, and the scope of this disclosure is not limited to them. Particular embodiments may include all, some, or none of the components, elements, features, functions, operations, or steps of the embodiments disclosed above. Embodiments according to the invention are in particular disclosed in the attached claims directed to a method, a storage medium, a system and a computer program product, wherein any feature mentioned in one claim category, e.g. method, can be claimed in another claim category, e.g. system, as well. The dependencies or references back in the attached claims are chosen for formal reasons only. However, any subject matter resulting from a deliberate reference back to any previous claims (in particular multiple dependencies) can be claimed as well, so that any combination of claims and the features thereof are disclosed and can be claimed regardless of the dependencies chosen in the attached claims. The subject-matter which can be claimed comprises not only the combinations of features as set out in the attached claims but also any other combination of features in the claims, wherein each feature mentioned in the claims can be combined with any other feature or combination of other features in the claims. Furthermore, any of the embodiments and features described or depicted herein can be claimed in a separate claim and/or in any combination with any embodiment or feature described or depicted herein or with any of the features of the attached claims.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates an example network environment associated with a social-networking system.

FIG. 2 illustrates an example social graph.

FIG. 3 illustrates an example system environment.

FIG. 4 illustrates a technique for utilizing multiple access points to determine a position of a client system.

FIG. 5 illustrates a peer-to-peer relay of a broadcasted signal from an access point.

FIG. 6 illustrates a client system receiving location updates based on a location of the client system and user data.

FIG. 7 illustrates a system environment, in which a client system is non-stationary.

FIG. 8 illustrates an example method for dynamic location update delivery.

FIG. 9 illustrates an example computer system.

DESCRIPTION OF EXAMPLE EMBODIMENTS

The disclosure relates to a technique for using access points to determine a location of a client system. In addition, the location of the client system may be used to select and display relevant location updates to a user.

FIG. 1 illustrates an example network environment 100 associated with a social-networking system. Network environment 100 includes a client system 130, a social-networking system 160, and a third-party system 170 connected to each other by a network 110. Although FIG. 1 illustrates a particular arrangement of client system 130, social-networking system 160, third-party system 170, and network 110, this disclosure contemplates any suitable arrangement of client system 130, social-networking system 160, third-party system 170, and network 110. As an example and not by way of limitation, two or more of client system 130, social-networking system 160, and third-party system 170 may be connected to each other directly, bypassing network 110. As another example, two or more of client system 130, social-networking system 160, and third-party system 170 may be physically or logically co-located with each other in whole or in part. Moreover, although FIG. 1 illustrates a particular number of client systems 130, social-networking systems 160, third-party systems 170, and networks 110, this disclosure contemplates any suitable number of client systems 130, social-networking systems 160, third-party systems 170, and networks 110. As an example and not by way of limitation, network environment 100 may include multiple client system 130, social-networking systems 160, third-party systems 170, and networks 110.

This disclosure contemplates any suitable network 110. As an example and not by way of limitation, one or more portions of network 110 may include an ad hoc network, an intranet, an extranet, a virtual private network (VPN), a local area network (LAN), a wireless LAN (WLAN), a wide area network (WAN), a wireless WAN (WWAN), a metropolitan area network (MAN), a portion of the Internet, a portion of the Public Switched Telephone Network (PSTN), a cellular telephone network, or a combination of two or more of these. Network 110 may include one or more networks 110.

Links 150 may connect client system 130, social-networking system 160, and third-party system 170 to communication network 110 or to each other. This disclosure contemplates any suitable links 150. In particular embodiments, one or more links 150 include one or more wireline (such as for example Digital Subscriber Line (DSL) or Data Over Cable Service Interface Specification (DOCSIS)), wireless (such as for example Wi-Fi or Worldwide Interoperability for Microwave Access (WiMAX)), or optical (such as for example Synchronous Optical Network (SONET) or Synchronous Digital Hierarchy (SDH)) links. In particular embodiments, one or more links 150 each include an ad hoc network, an intranet, an extranet, a VPN, a LAN, a WLAN, a WAN, a WWAN, a MAN, a portion of the Internet, a portion of the PSTN, a cellular technology-based network, a satellite communications technology-based network, another link 150, or a combination of two or more such links 150. Links 150 need not necessarily be the same throughout network environment 100. One or more first links 150 may differ in one or more respects from one or more second links 150.

In particular embodiments, client system 130 may be an electronic device including hardware, software, or embedded logic components or a combination of two or more such components and capable of carrying out the appropriate functionalities implemented or supported by client system 130. As an example and not by way of limitation, a client system 130 may include a computer system such as a desktop computer, notebook or laptop computer, netbook, a tablet computer, e-book reader, GPS device, camera, personal digital assistant (PDA), handheld electronic device, cellular telephone, smartphone, augmented/virtual reality device, other suitable electronic device, or any suitable combination thereof. This disclosure contemplates any suitable client systems 130. A client system 130 may enable a network user at client system 130 to access network 110. A client system 130 may enable its user to communicate with other users at other client systems 130.

In particular embodiments, client system 130 may include a web browser 132, such as MICROSOFT INTERNET EXPLORER, GOOGLE CHROME or MOZILLA FIREFOX, and may have one or more add-ons, plug-ins, or other extensions, such as TOOLBAR or YAHOO TOOLBAR. A user at client system 130 may enter a Uniform Resource Locator (URL) or other address directing the web browser 132 to a particular server (such as server 162, or a server associated with a third-party system 170), and the web browser 132 may generate a Hyper Text Transfer Protocol (HTTP) request and communicate the HTTP request to server. The server may accept the HTTP request and communicate to client system 130 one or more Hyper Text Markup Language (HTML) files responsive to the HTTP request. Client system 130 may render a webpage based on the HTML files from the server for presentation to the user. This disclosure contemplates any suitable webpage files. As an example and not by way of limitation, webpages may render from HTML files, Extensible Hyper Text Markup Language (XHTML) files, or Extensible Markup Language (XML) files, according to particular needs. Such pages may also execute scripts such as, for example and without limitation, those written in JAVASCRIPT, JAVA, MICROSOFT SILVERLIGHT, combinations of markup language and scripts such as AJAX (Asynchronous JAVASCRIPT and XML), and the like. Herein, reference to a webpage encompasses one or more corresponding webpage files (which a browser may use to render the webpage) and vice versa, where appropriate.

In particular embodiments, social-networking system 160 may be a network-addressable computing system that can host an online social network. Social-networking system 160 may generate, store, receive, and send social-networking data, such as, for example, user-profile data, concept-profile data, social-graph information, or other suitable data related to the online social network. Social-networking system 160 may be accessed by the other components of network environment 100 either directly or via network 110. As an example and not by way of limitation, client system 130 may access social-networking system 160 using a web browser 132, or a native application associated with social-networking system 160 (e.g., a mobile social-networking application, a messaging application, another suitable application, or any combination thereof) either directly or via network 110. In particular embodiments, social-networking system 160 may include one or more servers 162. Each server 162 may be a unitary server or a distributed server spanning multiple computers or multiple datacenters. Servers 162 may be of various types, such as, for example and without limitation, web server, news server, mail server, message server, advertising server, file server, application server, exchange server, database server, proxy server, another server suitable for performing functions or processes described herein, or any combination thereof. In particular embodiments, each server 162 may include hardware, software, or embedded logic components or a combination of two or more such components for carrying out the appropriate functionalities implemented or supported by server 162. In particular embodiments, social-networking system 160 may include one or more data stores 164. Data stores 164 may be used to store various types of information. In particular embodiments, the information stored in data stores 164 may be organized according to specific data structures. In particular embodiments, each data store 164 may be a relational, columnar, correlation, or other suitable database. Although this disclosure describes or illustrates particular types of databases, this disclosure contemplates any suitable types of databases. Particular embodiments may provide interfaces that enable a client system 130, a social-networking system 160, or a third-party system 170 to manage, retrieve, modify, add, or delete, the information stored in data store 164.

In particular embodiments, social-networking system 160 may store one or more social graphs in one or more data stores 164. In particular embodiments, a social graph may include multiple nodes—which may include multiple user nodes (each corresponding to a particular user) or multiple concept nodes (each corresponding to a particular concept)—and multiple edges connecting the nodes. Social-networking system 160 may provide users of the online social network the ability to communicate and interact with other users. In particular embodiments, users may join the online social network via social-networking system 160 and then add connections (e.g., relationships) to a number of other users of social-networking system 160 to whom they want to be connected. Herein, the term “friend” may refer to any other user of social-networking system 160 with whom a user has formed a connection, association, or relationship via social-networking system 160.

In particular embodiments, social-networking system 160 may provide users with the ability to take actions on various types of items or objects, supported by social-networking system 160. As an example and not by way of limitation, the items and objects may include groups or social networks to which users of social-networking system 160 may belong, events or calendar entries in which a user might be interested, computer-based applications that a user may use, transactions that allow users to buy or sell items via the service, interactions with advertisements that a user may perform, or other suitable items or objects. A user may interact with anything that is capable of being represented in social-networking system 160 or by an external system of third-party system 170, which is separate from social-networking system 160 and coupled to social-networking system 160 via a network 110.

In particular embodiments, social-networking system 160 may be capable of linking a variety of entities. As an example and not by way of limitation, social-networking system 160 may enable users to interact with each other as well as receive content from third-party systems 170 or other entities, or to allow users to interact with these entities through an application programming interfaces (API) or other communication channels.

In particular embodiments, a third-party system 170 may include one or more types of servers, one or more data stores, one or more interfaces, including but not limited to APIs, one or more web services, one or more content sources, one or more networks, or any other suitable components, e.g., that servers may communicate with. A third-party system 170 may be operated by a different entity from an entity operating social-networking system 160. In particular embodiments, however, social-networking system 160 and third-party systems 170 may operate in conjunction with each other to provide social-networking services to users of social-networking system 160 or third-party systems 170. In this sense, social-networking system 160 may provide a platform, or backbone, which other systems, such as third-party systems 170, may use to provide social-networking services and functionality to users across the Internet.

In particular embodiments, a third-party system 170 may include a third-party content object provider. A third-party content object provider may include one or more sources of content objects, which may be communicated to a client system 130. As an example and not by way of limitation, content objects may include information regarding things or activities of interest to the user, such as, for example, movie show times, movie reviews, restaurant reviews, restaurant menus, product information and reviews, or other suitable information. As another example and not by way of limitation, content objects may include incentive content objects, such as coupons, discount tickets, gift certificates, or other suitable incentive objects.

In particular embodiments, social-networking system 160 also includes user-generated content objects, which may enhance a user's interactions with social-networking system 160. User-generated content may include anything a user can add, upload, send, or “post” to social-networking system 160. As an example and not by way of limitation, a user communicates posts to social-networking system 160 from a client system 130. Posts may include data such as status updates or other textual data, location information, photos, videos, links, music or other similar data or media. Content may also be added to social-networking system 160 by a third-party through a “communication channel,” such as a newsfeed or stream.

In particular embodiments, social-networking system 160 may include a variety of servers, sub-systems, programs, modules, logs, and data stores. In particular embodiments, social-networking system 160 may include one or more of the following: a web server, action logger, API-request server, relevance-and-ranking engine, content-object classifier, notification controller, action log, third-party-content-object-exposure log, inference module, authorization/privacy server, search module, advertisement-targeting module, user-interface module, user-profile store, connection store, third-party content store, or location store. Social-networking system 160 may also include suitable components such as network interfaces, security mechanisms, load balancers, failover servers, management-and-network-operations consoles, other suitable components, or any suitable combination thereof. In particular embodiments, social-networking system 160 may include one or more user-profile stores for storing user profiles. A user profile may include, for example, biographic information, demographic information, behavioral information, social information, or other types of descriptive information, such as work experience, educational history, hobbies or preferences, interests, affinities, or location. Interest information may include interests related to one or more categories. Categories may be general or specific. As an example and not by way of limitation, if a user “likes” an article about a brand of shoes the category may be the brand, or the general category of “shoes” or “clothing.” A connection store may be used for storing connection information about users. The connection information may indicate users who have similar or common work experience, group memberships, hobbies, educational history, or are in any way related or share common attributes. The connection information may also include user-defined connections between different users and content (both internal and external). A web server may be used for linking social-networking system 160 to one or more client systems 130 or one or more third-party system 170 via network 110. The web server may include a mail server or other messaging functionality for receiving and routing messages between social-networking system 160 and one or more client systems 130. An API-request server may allow a third-party system 170 to access information from social-networking system 160 by calling one or more APIs. An action logger may be used to receive communications from a web server about a user's actions on or off social-networking system 160. In conjunction with the action log, a third-party-content-object log may be maintained of user exposures to third-party-content objects. A notification controller may provide information regarding content objects to a client system 130. Information may be pushed to a client system 130 as notifications, or information may be pulled from client system 130 responsive to a request received from client system 130. Authorization servers may be used to enforce one or more privacy settings of the users of social-networking system 160. A privacy setting of a user determines how particular information associated with a user can be shared. The authorization server may allow users to opt in to or opt out of having their actions logged by social-networking system 160 or shared with other systems (e.g., third-party system 170), such as, for example, by setting appropriate privacy settings. Third-party-content-object stores may be used to store content objects received from third parties, such as a third-party system 170. Location stores may be used for storing location information received from client systems 130 associated with users. Advertisement-pricing modules may combine social information, the current time, location information, or other suitable information to provide relevant advertisements, in the form of notifications, to a user.

In particular embodiments, an advertisement may be text (which may be HTML-linked), one or more images (which may be HTML-linked), one or more videos, audio, other suitable digital object files, a suitable combination of these, or any other suitable advertisement in any suitable digital format presented on one or more web pages, in one or more e-mails, or in connection with search results requested by a user. In addition or as an alternative, an advertisement may be one or more sponsored stories (e.g., a news-feed or ticker item on social-networking system 160). A sponsored story may be a social action by a user (such as “liking” a page, “liking” or commenting on a post on a page, RSVPing to an event associated with a page, voting on a question posted on a page, checking in to a place, using an application or playing a game, or “liking” or sharing a website) that an advertiser promotes, for example, by having the social action presented within a pre-determined area of a profile page of a user or other page, presented with additional information associated with the advertiser, bumped up or otherwise highlighted within news feeds or tickers of other users, or otherwise promoted. The advertiser may pay to have the social action promoted. The social action may be promoted within or on social-networking system 160. In addition or as an alternative, the social action may be promoted outside or off of social-networking system 160, where appropriate. In particular embodiments, a page may be an on-line presence (such as a webpage or website within or outside of social-networking system 160) of a business, organization, or brand facilitating its sharing of stories and connecting with people. A page may be customized, for example, by adding applications, posting stories, or hosting events.

A sponsored story may be generated from stories in users' news feeds and promoted to specific areas within displays of users' web browsers when viewing a web page associated with social-networking system 160. Sponsored stories are more likely to be viewed by users, at least in part because sponsored stories generally involve interactions or suggestions by the users' friends, fan pages, or other connections. In connection with sponsored stories, particular embodiments may utilize one or more systems, components, elements, functions, methods, operations, or steps disclosed in U.S. patent application Ser. No. 13/327,557, entitled “Sponsored Stories Unit Creation from Organic Activity Stream” and filed 15 Dec. 2011, U.S. Patent Application Publication No. 2012/0203831, entitled “Sponsored Stories Unit Creation from Organic Activity Stream” and filed 3 Feb. 2012 as U.S. patent application Ser. No. 13/020,745, or U.S. Patent Application Publication No. 2012/0233009, entitled “Endorsement Subscriptions for Sponsored Stories” and filed 9 Mar. 2011 as U.S. patent application Ser. No. 13/044,506, which are all incorporated herein by reference as an example and not by way of limitation. In particular embodiments, sponsored stories may utilize computer-vision algorithms to detect products in uploaded images or photos lacking an explicit connection to an advertiser as disclosed in U.S. patent application Ser. No. 13/212,356, entitled “Computer-Vision Content Detection for Sponsored Stories” and filed 18 Aug. 2011, which is incorporated herein by reference as an example and not by way of limitation.

As described above, an advertisement may be text (which may be HTML-linked), one or more images (which may be HTML-linked), one or more videos, audio, one or more ADOBE FLASH files, a suitable combination of these, or any other suitable advertisement in any suitable digital format. In particular embodiments, an advertisement may be requested for display within third-party webpages, social-networking-system webpages, or other pages. An advertisement may be displayed in a dedicated portion of a page, such as in a banner area at the top of the page, in a column at the side of the page, in a GUI of the page, in a pop-up window, over the top of content of the page, or elsewhere with respect to the page. In addition or as an alternative, an advertisement may be displayed within an application or within a game. An advertisement may be displayed within dedicated pages, requiring the user to interact with or watch the advertisement before the user may access a page, utilize an application, or play a game. The user may, for example view the advertisement through a web browser.

A user may interact with an advertisement in any suitable manner. The user may click or otherwise select the advertisement, and the advertisement may direct the user (or a browser or other application being used by the user) to a page associated with the advertisement. At the page associated with the advertisement, the user may take additional actions, such as purchasing a product or service associated with the advertisement, receiving information associated with the advertisement, or subscribing to a newsletter associated with the advertisement. An advertisement with audio or video may be played by selecting a component of the advertisement (like a “play button”). In particular embodiments, an advertisement may include one or more games, which a user or other application may play in connection with the advertisement. An advertisement may include functionality for responding to a poll or question in the advertisement.

An advertisement may include social-networking-system functionality that a user may interact with. For example, an advertisement may enable a user to “like” or otherwise endorse the advertisement by selecting an icon or link associated with endorsement. Similarly, a user may share the advertisement with another user (e.g., through social-networking system 160) or RSVP (e.g., through social-networking system 160) to an event associated with the advertisement. In addition or as an alternative, an advertisement may include social-networking-system content directed to the user. For example, an advertisement may display information about a friend of the user within social-networking system 160 who has taken an action associated with the subject matter of the advertisement.

Social-networking-system functionality or content may be associated with an advertisement in any suitable manner. For example, an advertising system (which may include hardware, software, or both for receiving bids for advertisements and selecting advertisements in response) may retrieve social-networking functionality or content from social-networking system 160 and incorporate the retrieved social-networking functionality or content into the advertisement before serving the advertisement to a user. Examples of selecting and providing social-networking-system functionality or content with an advertisement are disclosed in U.S. Patent Application Publication No. 2012/0084160, entitled “Providing Social Endorsements with Online Advertising” and filed 5 Oct. 2010 as U.S. patent application Ser. No. 12/898,662, and in U.S. Patent Application Publication No. 2012/0232998, entitled “Selecting Social Endorsement Information for an Advertisement for Display to a Viewing User” and filed 8 Mar. 2011 as U.S. patent application Ser. No. 13/043,424, which are both incorporated herein by reference as examples only and not by way of limitation. Interacting with an advertisement that is associated with social-networking-system functionality or content may cause information about the interaction to be displayed in a profile page of the user in social-networking-system 160.

Particular embodiments may facilitate the delivery of advertisements to users that are more likely to find the advertisements more relevant or useful. For example, an advertiser may realize higher conversion rates (and therefore higher return on investment (ROI) from advertising) by identifying and targeting users that are more likely to find its advertisements more relevant or useful. The advertiser may use user-profile information in social-networking system 160 to identify those users. In addition or as an alternative, social-networking system 160 may use user-profile information in social-networking system 160 to identify those users for the advertiser. As examples and not by way of limitation, particular embodiments may target users with the following: invitations or suggestions of events; suggestions regarding coupons, deals, or wish-list items; suggestions regarding friends' life events; suggestions regarding groups; advertisements; or social advertisements. Such targeting may occur, where appropriate, on or within social-networking system 160, off or outside of social-networking system 160, or on mobile computing devices of users. When on or within social-networking system 160, such targeting may be directed to users' news feeds, search results, e-mail or other in-boxes, or notifications channels or may appear in particular area of web pages of social-networking system 160, such as a right-hand side of a web page in a concierge or grouper area (which may group along a right-hand rail advertisements associated with the same concept, node, or object) or a network-ego area (which may be based on what a user is viewing on the web page and a current news feed of the user). When off or outside of social-networking system 160, such targeting may be provided through a third-party website, e.g., involving an ad exchange or a social plug-in. When on a mobile computing device of a user, such targeting may be provided through push notifications to the mobile computing device.

Targeting criteria used to identify and target users may include explicit, stated user interests on social-networking system 160 or explicit connections of a user to a node, object, entity, brand, or page on social-networking system 160. In addition or as an alternative, such targeting criteria may include implicit or inferred user interests or connections (which may include analyzing a user's history, demographic, social or other activities, friends' social or other activities, subscriptions, or any of the preceding of other users similar to the user (based, e.g., on shared interests, connections, or events)). Particular embodiments may utilize platform targeting, which may involve platform and “like” impression data; contextual signals (e.g., “Who is viewing now or has viewed recently the page for COCA-COLA?”); light-weight connections (e.g., “check-ins”); connection lookalikes; fans; extracted keywords; EMU advertising; inferential advertising; coefficients, affinities, or other social-graph information; friends-of-friends connections; pinning or boosting; deals; polls; household income, social clusters or groups; products detected in images or other media; social- or open-graph edge types; geo-prediction; views of profile or pages; status updates or other user posts (analysis of which may involve natural-language processing or keyword extraction); events information; or collaborative filtering. Identifying and targeting users may also include privacy settings (such as user opt-outs), data hashing, or data anonymization, as appropriate.

To target users with advertisements, particular embodiments may utilize one or more systems, components, elements, functions, methods, operations, or steps disclosed in the following, which are all incorporated herein by reference as examples and not by way of limitation: U.S. Patent Application Publication No. 2009/0119167, entitled “Social Advertisements and Other Informational Messages on a Social Networking Website and Advertising Model for Same” and filed 18 Aug. 2008 as U.S. patent application Ser. No. 12/193,702; U.S. Patent Application Publication No. 2009/0070219, entitled “Targeting Advertisements in a Social Network” and filed 20 Aug. 2008 as U.S. patent application Ser. No. 12/195,321; U.S. Patent Application Publication No. 2012/0158501, entitled “Targeting Social Advertising to Friends of Users Who Have Interacted With an Object Associated with the Advertising” and filed 15 Dec. 2010 as U.S. patent application Ser. No. 12/968,786; or U.S. Patent Application Publication No. 2012/0166532, entitled “Contextually Relevant Affinity Prediction in a Social-Networking System” and filed 23 Dec. 2010 as U.S. patent application Ser. No. 12/978,265.

An advertisement may be presented or otherwise delivered using plug-ins for web browsers or other applications, iframe elements, news feeds, tickers, notifications (which may include, for example, e-mail, Short Message Service (SMS) messages, or notifications), or other means. An advertisement may be presented or otherwise delivered to a user on a mobile or other computing device of the user. In connection with delivering advertisements, particular embodiments may utilize one or more systems, components, elements, functions, methods, operations, or steps disclosed in the following, which are all incorporated herein by reference as examples and not by way of limitation: U.S. Patent Application Publication No. 2012/0159635, entitled “Comment Plug-In for Third-Party System” and filed 15 Dec. 2010 as U.S. patent application Ser. No. 12/969,368; U.S. Patent Application Publication No. 2012/0158753, entitled “Comment Ordering System” and filed 15 Dec. 2010 as U.S. patent application Ser. No. 12/969,408; U.S. Pat. No. 7,669,123, entitled “Dynamically Providing a News Feed About a User of a Social Network” and filed 11 Aug. 2006 as U.S. patent application Ser. No. 11/503,242; U.S. Pat. No. 8,402,094, entitled “Providing a Newsfeed Based on User Affinity for Entities and Monitored Actions in a Social Network Environment” and filed 11 Aug. 2006 as U.S. patent application Ser. No. 11/503,093; U.S. Patent Application Publication No. 2012/0072428, entitled “Action Clustering for News Feeds” and filed 16 Sep. 2010 as U.S. patent application Ser. No. 12/884,010; U.S. Patent Application Publication No. 2011/0004692, entitled “Gathering Information about Connections in a Social Networking Service” and filed 1 Jul. 2009 as U.S. patent application Ser. No. 12/496,606; U.S. Patent Application Publication No. 2008/0065701, entitled “Method and System for Tracking Changes to User Content in an Online Social Network” and filed 12 Sep. 2006 as U.S. patent application Ser. No. 11/531,154; U.S. Patent Application Publication No. 2008/0065604, entitled “Feeding Updates to Landing Pages of Users of an Online Social Network from External Sources” and filed 17 Jan. 2007 as U.S. patent application Ser. No. 11/624,088; U.S. Pat. No. 8,244,848, entitled “Integrated Social-Network Environment” and filed 19 Apr. 2010 as U.S. patent application Ser. No. 12/763,171; U.S. Patent Application Publication No. 2011/0083101, entitled “Sharing of Location-Based Content Item in Social-Networking Service” and filed 6 Oct. 2009 as U.S. patent application Ser. No. 12/574,614; U.S. Pat. No. 8,150,844, entitled “Location Ranking Using Social-Graph Information” and filed 18 Aug. 2010 as U.S. patent application Ser. No. 12/858,718; U.S. patent application Ser. No. 13/051,286, entitled “Sending Notifications to Users Based on Users' Notification Tolerance Levels” and filed 18 Mar. 2011; U.S. patent application Ser. No. 13/096,184, entitled “Managing Notifications Pushed to User Devices” and filed 28 Apr. 2011; U.S. patent application Ser. No. 13/276,248, entitled “Platform-Specific Notification Delivery Channel” and filed 18 Oct. 2011; or U.S. Patent Application Publication No. 2012/0197709, entitled “Mobile Advertisement with Social Component for Geo-Social Networking System” and filed 1 Feb. 2011 as U.S. patent application Ser. No. 13/019,061. Although this disclosure describes or illustrates particular advertisements being delivered in particular ways and in connection with particular content, this disclosure contemplates any suitable advertisements delivered in any suitable ways and in connection with any suitable content.

FIG. 2 illustrates example social graph 200. In particular embodiments, social-networking system 160 may store one or more social graphs 200 in one or more data stores. In particular embodiments, social graph 200 may include multiple nodes—which may include multiple user nodes 202 or multiple concept nodes 204—and multiple edges 206 connecting the nodes. Each node may be associated with a unique entity (i.e., user or concept), each of which may have a unique identifier (ID), such as a unique number or username. Example social graph 200 illustrated in FIG. 2 is shown, for didactic purposes, in a two-dimensional visual map representation. In particular embodiments, a social-networking system 160, client system 130, or third-party system 170 may access social graph 200 and related social-graph information for suitable applications. The nodes and edges of social graph 200 may be stored as data objects, for example, in a data store (such as a social-graph database). Such a data store may include one or more searchable or queryable indexes of nodes or edges of social graph 200.

In particular embodiments, a user node 202 may correspond to a user of social-networking system 160. As an example and not by way of limitation, a user may be an individual (human user), an entity (e.g., an enterprise, business, or third-party application), or a group (e.g., of individuals or entities) that interacts or communicates with or over social-networking system 160. In particular embodiments, when a user registers for an account with social-networking system 160, social-networking system 160 may create a user node 202 corresponding to the user and store the user node 202 in one or more data stores. Users and user nodes 202 described herein may, where appropriate, refer to registered users and user nodes 202 associated with registered users. In addition or as an alternative, users and user nodes 202 described herein may, where appropriate, refer to users that have not registered with social-networking system 160. In particular embodiments, a user node 202 may be associated with information provided by a user or information gathered by various systems, including social-networking system 160. As an example and not by way of limitation, a user may provide his or her name, profile picture, contact information, birth date, sex, marital status, family status, employment, education background, preferences, interests, or other demographic information. In particular embodiments, a user node 202 may be associated with one or more data objects corresponding to information associated with a user. In particular embodiments, a user node 202 may correspond to one or more webpages.

In particular embodiments, a concept node 204 may correspond to a concept. As an example and not by way of limitation, a concept may correspond to a place (such as, for example, a movie theater, restaurant, landmark, or city); a website (such as, for example, a website associated with social-network system 160 or a third-party website associated with a web-application server); an entity (such as, for example, a person, business, group, sports team, or celebrity); a resource (such as, for example, an audio file, video file, digital photo, text file, structured document, or application) which may be located within social-networking system 160 or on an external server, such as a web-application server; real or intellectual property (such as, for example, a sculpture, painting, movie, game, song, idea, photograph, or written work); a game; an activity; an idea or theory; an object in a augmented/virtual reality environment; another suitable concept; or two or more such concepts. A concept node 204 may be associated with information of a concept provided by a user or information gathered by various systems, including social-networking system 160. As an example and not by way of limitation, information of a concept may include a name or a title; one or more images (e.g., an image of the cover page of a book); a location (e.g., an address or a geographical location); a website (which may be associated with a URL); contact information (e.g., a phone number or an email address); other suitable concept information; or any suitable combination of such information. In particular embodiments, a concept node 204 may be associated with one or more data objects corresponding to information associated with concept node 204. In particular embodiments, a concept node 204 may correspond to one or more webpages.

In particular embodiments, a node in social graph 200 may represent or be represented by a webpage (which may be referred to as a “profile page”). Profile pages may be hosted by or accessible to social-networking system 160. Profile pages may also be hosted on third-party websites associated with a third-party system 170. As an example and not by way of limitation, a profile page corresponding to a particular external webpage may be the particular external webpage and the profile page may correspond to a particular concept node 204. Profile pages may be viewable by all or a selected subset of other users. As an example and not by way of limitation, a user node 202 may have a corresponding user-profile page in which the corresponding user may add content, make declarations, or otherwise express himself or herself. As another example and not by way of limitation, a concept node 204 may have a corresponding concept-profile page in which one or more users may add content, make declarations, or express themselves, particularly in relation to the concept corresponding to concept node 204.

In particular embodiments, a concept node 204 may represent a third-party webpage or resource hosted by a third-party system 170. The third-party webpage or resource may include, among other elements, content, a selectable or other icon, or other inter-actable object (which may be implemented, for example, in JavaScript, AJAX, or PHP codes) representing an action or activity. As an example and not by way of limitation, a third-party webpage may include a selectable icon such as “like,” “check-in,” “eat,” “recommend,” or another suitable action or activity. A user viewing the third-party webpage may perform an action by selecting one of the icons (e.g., “check-in”), causing a client system 130 to send to social-networking system 160 a message indicating the user's action. In response to the message, social-networking system 160 may create an edge (e.g., a check-in-type edge) between a user node 202 corresponding to the user and a concept node 204 corresponding to the third-party webpage or resource and store edge 206 in one or more data stores.

In particular embodiments, a pair of nodes in social graph 200 may be connected to each other by one or more edges 206. An edge 206 connecting a pair of nodes may represent a relationship between the pair of nodes. In particular embodiments, an edge 206 may include or represent one or more data objects or attributes corresponding to the relationship between a pair of nodes. As an example and not by way of limitation, a first user may indicate that a second user is a “friend” of the first user. In response to this indication, social-networking system 160 may send a “friend request” to the second user. If the second user confirms the “friend request,” social-networking system 160 may create an edge 206 connecting the first user's user node 202 to the second user's user node 202 in social graph 200 and store edge 206 as social-graph information in one or more of data stores 164. In the example of FIG. 2, social graph 200 includes an edge 206 indicating a friend relation between user nodes 202 of user “A” and user “B” and an edge indicating a friend relation between user nodes 202 of user “C” and user “B.” Although this disclosure describes or illustrates particular edges 206 with particular attributes connecting particular user nodes 202, this disclosure contemplates any suitable edges 206 with any suitable attributes connecting user nodes 202. As an example and not by way of limitation, an edge 206 may represent a friendship, family relationship, business or employment relationship, fan relationship (including, e.g., liking, etc.), follower relationship, visitor relationship (including, e.g., accessing, viewing, checking-in, sharing, etc.), subscriber relationship, superior/subordinate relationship, reciprocal relationship, non-reciprocal relationship, another suitable type of relationship, or two or more such relationships. Moreover, although this disclosure generally describes nodes as being connected, this disclosure also describes users or concepts as being connected. Herein, references to users or concepts being connected may, where appropriate, refer to the nodes corresponding to those users or concepts being connected in social graph 200 by one or more edges 206. The degree of separation between two objects represented by two nodes, respectively, is a count of edges in a shortest path connecting the two nodes in the social graph 200. As an example and not by way of limitation, in the social graph 200, the user node 202 of user “C” is connected to the user node 202 of user “A” via multiple paths including, for example, a first path directly passing through the user node 202 of user “B,” a second path passing through the concept node 204 of company “Acme” and the user node 202 of user “D,” and a third path passing through the user nodes 202 and concept nodes 204 representing school “Stanford,” user “G,” company “Acme,” and user “D.” User “C” and user “A” have a degree of separation of two because the shortest path connecting their corresponding nodes (i.e., the first path) includes two edges 206.

In particular embodiments, an edge 206 between a user node 202 and a concept node 204 may represent a particular action or activity performed by a user associated with user node 202 toward a concept associated with a concept node 204. As an example and not by way of limitation, as illustrated in FIG. 2, a user may “like,” “attended,” “played,” “listened,” “cooked,” “worked at,” or “watched” a concept, each of which may correspond to an edge type or subtype. A concept-profile page corresponding to a concept node 204 may include, for example, a selectable “check in” icon (such as, for example, a clickable “check in” icon) or a selectable “add to favorites” icon. Similarly, after a user clicks these icons, social-networking system 160 may create a “favorite” edge or a “check in” edge in response to a user's action corresponding to a respective action. As another example and not by way of limitation, a user (user “C”) may listen to a particular song (“Imagine”) using a particular application (SPOTIFY, which is an online music application). In this case, social-networking system 160 may create a “listened” edge 206 and a “used” edge (as illustrated in FIG. 2) between user nodes 202 corresponding to the user and concept nodes 204 corresponding to the song and application to indicate that the user listened to the song and used the application. Moreover, social-networking system 160 may create a “played” edge 206 (as illustrated in FIG. 2) between concept nodes 204 corresponding to the song and the application to indicate that the particular song was played by the particular application. In this case, “played” edge 206 corresponds to an action performed by an external application (SPOTTY) on an external audio file (the song “Imagine”). Although this disclosure describes particular edges 206 with particular attributes connecting user nodes 202 and concept nodes 204, this disclosure contemplates any suitable edges 206 with any suitable attributes connecting user nodes 202 and concept nodes 204. Moreover, although this disclosure describes edges between a user node 202 and a concept node 204 representing a single relationship, this disclosure contemplates edges between a user node 202 and a concept node 204 representing one or more relationships. As an example and not by way of limitation, an edge 206 may represent both that a user likes and has used at a particular concept. Alternatively, another edge 206 may represent each type of relationship (or multiples of a single relationship) between a user node 202 and a concept node 204 (as illustrated in FIG. 2 between user node 202 for user “E” and concept node 204 for “SPOTIFY”).

In particular embodiments, social-networking system 160 may create an edge 206 between a user node 202 and a concept node 204 in social graph 200. As an example and not by way of limitation, a user viewing a concept-profile page (such as, for example, by using a web browser or a special-purpose application hosted by the user's client system 130) may indicate that he or she likes the concept represented by the concept node 204 by clicking or selecting a “Like” icon, which may cause the user's client system 130 to send to social-networking system 160 a message indicating the user's liking of the concept associated with the concept-profile page. In response to the message, social-networking system 160 may create an edge 206 between user node 202 associated with the user and concept node 204, as illustrated by “like” edge 206 between the user and concept node 204. In particular embodiments, social-networking system 160 may store an edge 206 in one or more data stores. In particular embodiments, an edge 206 may be automatically formed by social-networking system 160 in response to a particular user action. As an example and not by way of limitation, if a first user uploads a picture, watches a movie, or listens to a song, an edge 206 may be formed between user node 202 corresponding to the first user and concept nodes 204 corresponding to those concepts. Although this disclosure describes forming particular edges 206 in particular manners, this disclosure contemplates forming any suitable edges 206 in any suitable manner.

In particular embodiments, social-networking system 160 may determine the social-graph affinity (which may be referred to herein as “affinity”) of various social-graph entities for each other. Affinity may represent the strength of a relationship or level of interest between particular objects associated with the online social network, such as users, concepts, content, actions, advertisements, other objects associated with the online social network, or any suitable combination thereof. Affinity may also be determined with respect to objects associated with third-party systems 170 or other suitable systems. An overall affinity for a social-graph entity for each user, subject matter, or type of content may be established. The overall affinity may change based on continued monitoring of the actions or relationships associated with the social-graph entity. Although this disclosure describes determining particular affinities in a particular manner, this disclosure contemplates determining any suitable affinities in any suitable manner.

In particular embodiments, social-networking system 160 may measure or quantify social-graph affinity using an affinity coefficient (which may be referred to herein as “coefficient”). The coefficient may represent or quantify the strength of a relationship between particular objects associated with the online social network. The coefficient may also represent a probability or function that measures a predicted probability that a user will perform a particular action based on the user's interest in the action. In this way, a user's future actions may be predicted based on the user's prior actions, where the coefficient may be calculated at least in part on the history of the user's actions. Coefficients may be used to predict any number of actions, which may be within or outside of the online social network. As an example and not by way of limitation, these actions may include various types of communications, such as sending messages, posting content, or commenting on content; various types of observation actions, such as accessing or viewing profile pages, media, or other suitable content; various types of coincidence information about two or more social-graph entities, such as being in the same group, tagged in the same photograph, checked-in at the same location, or attending the same event; or other suitable actions. Although this disclosure describes measuring affinity in a particular manner, this disclosure contemplates measuring affinity in any suitable manner.

In particular embodiments, social-networking system 160 may use a variety of factors to calculate a coefficient. These factors may include, for example, user actions, types of relationships between objects, location information, other suitable factors, or any combination thereof. In particular embodiments, different factors may be weighted differently when calculating the coefficient. The weights for each factor may be static or the weights may change according to, for example, the user, the type of relationship, the type of action, the user's location, and so forth. Ratings for the factors may be combined according to their weights to determine an overall coefficient for the user. As an example and not by way of limitation, particular user actions may be assigned both a rating and a weight while a relationship associated with the particular user action is assigned a rating and a correlating weight (e.g., so the weights total 100%). To calculate the coefficient of a user towards a particular object, the rating assigned to the user's actions may comprise, for example, 60% of the overall coefficient, while the relationship between the user and the object may comprise 40% of the overall coefficient. In particular embodiments, the social-networking system 160 may consider a variety of variables when determining weights for various factors used to calculate a coefficient, such as, for example, the time since information was accessed, decay factors, frequency of access, relationship to information or relationship to the object about which information was accessed, relationship to social-graph entities connected to the object, short- or long-term averages of user actions, user feedback, other suitable variables, or any combination thereof. As an example and not by way of limitation, a coefficient may include a decay factor that causes the strength of the signal provided by particular actions to decay with time, such that more recent actions are more relevant when calculating the coefficient. The ratings and weights may be continuously updated based on continued tracking of the actions upon which the coefficient is based. Any type of process or algorithm may be employed for assigning, combining, averaging, and so forth the ratings for each factor and the weights assigned to the factors. In particular embodiments, social-networking system 160 may determine coefficients using machine-learning algorithms trained on historical actions and past user responses, or data farmed from users by exposing them to various options and measuring responses. Although this disclosure describes calculating coefficients in a particular manner, this disclosure contemplates calculating coefficients in any suitable manner.

In particular embodiments, social-networking system 160 may calculate a coefficient based on a user's actions. Social-networking system 160 may monitor such actions on the online social network, on a third-party system 170, on other suitable systems, or any combination thereof. Any suitable type of user actions may be tracked or monitored. Typical user actions include viewing profile pages, creating or posting content, interacting with content, tagging or being tagged in images, joining groups, listing and confirming attendance at events, checking-in at locations, liking particular pages, creating pages, and performing other tasks that facilitate social action. In particular embodiments, social-networking system 160 may calculate a coefficient based on the user's actions with particular types of content. The content may be associated with the online social network, a third-party system 170, or another suitable system. The content may include users, profile pages, posts, news stories, headlines, instant messages, chat room conversations, emails, advertisements, pictures, video, music, other suitable objects, or any combination thereof. Social-networking system 160 may analyze a user's actions to determine whether one or more of the actions indicate an affinity for subject matter, content, other users, and so forth. As an example and not by way of limitation, if a user frequently posts content related to “coffee” or variants thereof, social-networking system 160 may determine the user has a high coefficient with respect to the concept “coffee”. Particular actions or types of actions may be assigned a higher weight and/or rating than other actions, which may affect the overall calculated coefficient. As an example and not by way of limitation, if a first user emails a second user, the weight or the rating for the action may be higher than if the first user simply views the user-profile page for the second user.

In particular embodiments, social-networking system 160 may calculate a coefficient based on the type of relationship between particular objects. Referencing the social graph 200, social-networking system 160 may analyze the number and/or type of edges 206 connecting particular user nodes 202 and concept nodes 204 when calculating a coefficient. As an example and not by way of limitation, user nodes 202 that are connected by a spouse-type edge (representing that the two users are married) may be assigned a higher coefficient than a user node 202 that are connected by a friend-type edge. In other words, depending upon the weights assigned to the actions and relationships for the particular user, the overall affinity may be determined to be higher for content about the user's spouse than for content about the user's friend. In particular embodiments, the relationships a user has with another object may affect the weights and/or the ratings of the user's actions with respect to calculating the coefficient for that object. As an example and not by way of limitation, if a user is tagged in a first photo, but merely likes a second photo, social-networking system 160 may determine that the user has a higher coefficient with respect to the first photo than the second photo because having a tagged-in-type relationship with content may be assigned a higher weight and/or rating than having a like-type relationship with content. In particular embodiments, social-networking system 160 may calculate a coefficient for a first user based on the relationship one or more second users have with a particular object. In other words, the connections and coefficients other users have with an object may affect the first user's coefficient for the object. As an example and not by way of limitation, if a first user is connected to or has a high coefficient for one or more second users, and those second users are connected to or have a high coefficient for a particular object, social-networking system 160 may determine that the first user should also have a relatively high coefficient for the particular object. In particular embodiments, the coefficient may be based on the degree of separation between particular objects. The lower coefficient may represent the decreasing likelihood that the first user will share an interest in content objects of the user that is indirectly connected to the first user in the social graph 200. As an example and not by way of limitation, social-graph entities that are closer in the social graph 200 (i.e., fewer degrees of separation) may have a higher coefficient than entities that are further apart in the social graph 200.

In particular embodiments, social-networking system 160 may calculate a coefficient based on location information. Objects that are geographically closer to each other may be considered to be more related or of more interest to each other than more distant objects. In particular embodiments, the coefficient of a user towards a particular object may be based on the proximity of the object's location to a current location associated with the user (or the location of a client system 130 of the user). A first user may be more interested in other users or concepts that are closer to the first user. As an example and not by way of limitation, if a user is one mile from an airport and two miles from a gas station, social-networking system 160 may determine that the user has a higher coefficient for the airport than the gas station based on the proximity of the airport to the user.

In particular embodiments, social-networking system 160 may perform particular actions with respect to a user based on coefficient information. Coefficients may be used to predict whether a user will perform a particular action based on the user's interest in the action. A coefficient may be used when generating or presenting any type of objects to a user, such as advertisements, search results, news stories, media, messages, notifications, or other suitable objects. The coefficient may also be utilized to rank and order such objects, as appropriate. In this way, social-networking system 160 may provide information that is relevant to user's interests and current circumstances, increasing the likelihood that they will find such information of interest. In particular embodiments, social-networking system 160 may generate content based on coefficient information. Content objects may be provided or selected based on coefficients specific to a user. As an example and not by way of limitation, the coefficient may be used to generate media for the user, where the user may be presented with media for which the user has a high overall coefficient with respect to the media object. As another example and not by way of limitation, the coefficient may be used to generate advertisements for the user, where the user may be presented with advertisements for which the user has a high overall coefficient with respect to the advertised object. In particular embodiments, social-networking system 160 may generate search results based on coefficient information. Search results for a particular user may be scored or ranked based on the coefficient associated with the search results with respect to the querying user. As an example and not by way of limitation, search results corresponding to objects with higher coefficients may be ranked higher on a search-results page than results corresponding to objects having lower coefficients.

In particular embodiments, social-networking system 160 may calculate a coefficient in response to a request for a coefficient from a particular system or process. To predict the likely actions a user may take (or may be the subject of) in a given situation, any process may request a calculated coefficient for a user. The request may also include a set of weights to use for various factors used to calculate the coefficient. This request may come from a process running on the online social network, from a third-party system 170 (e.g., via an API or other communication channel), or from another suitable system. In response to the request, social-networking system 160 may calculate the coefficient (or access the coefficient information if it has previously been calculated and stored). In particular embodiments, social-networking system 160 may measure an affinity with respect to a particular process. Different processes (both internal and external to the online social network) may request a coefficient for a particular object or set of objects. Social-networking system 160 may provide a measure of affinity that is relevant to the particular process that requested the measure of affinity. In this way, each process receives a measure of affinity that is tailored for the different context in which the process will use the measure of affinity.

In connection with social-graph affinity and affinity coefficients, particular embodiments may utilize one or more systems, components, elements, functions, methods, operations, or steps disclosed in U.S. patent application Ser. No. 11/503,093, filed 11 Aug. 2006, U.S. patent application Ser. No. 12/977,027, filed 22 Dec. 2010, U.S. patent application Ser. No. 12/978,265, filed 23 Dec. 2010, and U.S. patent application Ser. No. 13/632,869, filed 1 Oct. 2012, each of which is incorporated by reference.

FIG. 3 illustrates an example system environment 300. System environment 300 includes emitter 310, global positioning system (GPS) signals 320, client system 130-1, client system 130-2, building 340, access point 360, and target destination 370. In various embodiments, emitter 310 outputs GPS signals 320 that are detected by client system 130-1 and client system 130-2 for navigation to target destination 370.

In particular, emitter 310 may refer to any object positioned above the earth surface that emits localization signals. For example, emitter 310 could include aircraft, such as airplanes and helicopters, spacecraft, such as satellites, localization signal emitters on hot air balloons and elevated locations, such as mountain tops, peaks, cellphone towers, and other elevated surfaces. In some embodiments, emitter 310 may include satellites located at various positions in and/or around the earth's atmosphere, including, for example and not by way of limitation, the upper earth atmosphere, the ionosphere, the near-earth orbit, the mid-earth orbit, and so forth. The emitter 310 may output signals to the earth surface. These signals may include low frequency electromagnetic waves that can travel through the earth's atmosphere, such as radio waves, microwaves, GPS signals 320, and so forth.

In addition, one or more devices may be configured to detect signals outputted by emitter 310. For example, client system 130-1 and client system 130-2 may each include a GPS sensor that detects GPS signals 320 emitted by emitter 310. In various embodiments, client system 130-1 may execute a mapping application installed on client system 130-1 to determine, based on the received GPS signals, a position of client system 130-1. Similarly, client system 130-2 may execute a mapping application to determine, based on the received GPS signals, a position of client system 130-2. A position of client system 130-1 may be included in a concept node associated with client system 130-1 and/or a user node associated with a user of client system 130-1. Similarly, a position of client system 130-2 may being included in both a concept node associated with client system 130-2 and a user node associated with a user of client system 130-2. Furthermore, a position of building 340 and a position of building 370 may also be included in separate concept nodes associated with building 340 and building 370, respectively. In various embodiments, a user of client system 130-1 may navigate to building 370 using the GPS-determined location of client system 130-1 and building 370.

However, in some embodiments, one or more objects may obstruct and/or reflect GPS signals en route to a client system. For example, building 340 may be located between client system 130-2 and emitter 310. Building 340 may absorb and/or reflect GPS signals en route to client system 130-2. Accordingly, mapping applications executed by client system 130-2 may not be able to accurately determine a position of client system 130-2. In such instances, the GPS-determined location of client system 130-2 may differ from the true location of client system 130-2 (e.g., by up to 500 meters or more). Accordingly, a user of client system 130-2 may become lost and unable to determine his or her location. In addition, mapping and/or navigation applications executed by client system 130-2 may malfunction because the position of client system 130-2 cannot be determined accurately.

In various embodiments, system environment 300 may include one or more access points 360. An access point 360 may include, for example and not by way of limitation, devices that produce local area network (LAN) signals and personal area network (PAN) signals, such as Wi-Fi®, Bluetooth® low energy, radio frequency ID, near field communications, infrared, and so forth. In particular, one or more access points 360 may be disposed within a broadcast distance of client system 130-2. For example, access point 360 may be a Bluetooth® low energy PAN that is within a broadcast distance of client system 130-2. Accordingly, client system 130-2 may be able to detect one or more signal attributes of the mobile hotspot. Signal attributes may include an access point identification number (ID).

In various embodiments, client system 130-2 may obtain access point data including some or all of an access point ID, a receiving signal strength, a broadcast frequency, a broadcast frequency range, a broadcast signal directionality, and so forth. Client system 130-2 can transfer the access point data to the social-networking system 160. The server 162 executes a localization application to receive access point data from the client system 130-2. In addition, the localization application searches through concept nodes 204 in social graph 200 to identify a concept node 204 associated with access point 360. The localization application identifies the location of access point 360 stored in concept node 204 and computes a location of client system 130-2 based on the access point location. The localization application transmits the computed location to client system 130-2. In so doing, the localization application enables relative positioning based off of local access point signals in the absence of GPS signal transmissions. This technique may be especially useful inside of buildings, in urban environments, and/or at locations where GPS signals are weak, while one or more access points 360 are within a broadcast range of client system 130-2.

In various embodiments, the localization application may also compute a location of building 370 and/or a path between the location of client system 130-2 and building 370. The localization application may also transmit the location of building 370 and/or the determined path between client system 130-2 and building 370 to client system 130-2. In various embodiments, the localization application may use the received signal strength of the access point signal detected by client system 130-2 to determine a relative distance between client system 130-2 and access point 360.

Additionally, or alternatively, the client system 130-2 may execute the localization application. Accordingly, the localization application may access the social graph via network 110 to identify one or more concept nodes 204 associated with a detected access point 360. In addition, the localization application may identify a location of access point 360 and building 370 from social graph 200 and compute a path between access point 360 and building 370.

FIG. 4 illustrates a technique for utilizing multiple access points 360 to determine a position of client system 130. In particular, system environment 400 includes access point 360-1, access point 360-2, and access point 360-3. In addition, each access point 360 has broadcast radius 460-1, 460-2, and 460-3, respectively. In addition, each access point 360-1, 360-2, and 360-3 has a relative distance 480-1, 480-2, and 480-3, from client system 130, respectively. Furthermore, system environment 400 includes triangulated position 470.

In operation, the client system 130 detects one or more access points that have a broadcast radius that is large enough to be detectable by client system 130. For example, in system environment 400, client system 130 is within a broadcast radius 460-1 of access point 360-1. Similarly, client system 130 is within a broadcast radius 460-2 and 460-3 of access points 360-2 and 360-3, respectively. As stated above, client system 130 receives access point data associated with each detected access point 360, including, but not limited to, an access point ID and a received signal strength. Client system 130 further transmits the access point data to the social-networking system 160. In various embodiments, the server 162 executes a localization application to receive the access point data and to identify a concept node 204 associated with each access point 360-1, 360-2, and 360-3. The localization application further identifies a location associated with each access point and calculates relative distances 480-1, 480-2, and 480-3 between each access point 360-1, 360-2, and 360-3 and client system 130, respectively.

In various embodiments, the localization application compares the received signal strength at the client system 130 with a radial broadcast intensity function to calculate a relative distance between the client system 130 and the access point 360-1, 360-2, or 360-3. For example, by identifying from social graph 200 a type of access point 360-1, 360-2, or 360-3 detected by client system 130, localization application could determine that a broadcast signal attenuates inversely proportionally to the square of the relative distance. Accordingly, by comparing the intensity of the outputted broadcast signal stored in social graph 200 to the received broadcast signal intensity, the localization application may calculate a relative distance between the access point 360-1, 360-2, or 360-3 and client system 130.

The localization application may calculate a relative distance 480-1, 480-2, and 480-3, between client system 130 and access point 360-1, 360-2, and 360-3, respectively. In addition, the localization application may further determine that the client system 130-2 is located at a position at which each of the relative distances 480-1, 480-2, and 480-3 intersect. For example, in system environment 400, the localization application may determine that the client system 130-2 is located at the triangulated position 470.

In further embodiments, client system 130 may determine an error associated with each relative distance 480-1, 480-2, and 480-3. Accordingly, the size of the triangulated position 470 may vary based on a determined error in the relative distances 480-1, 480-2, and 480-3. In various embodiments, the size of the triangulated position 470 decreases as the number of detected access points increase. Accordingly, the localization application may determine a relative distance 480 for as many access points 360 as the client system 130 can detect in order to obtain a precise determination of the true location of client system 130.

In some embodiments, the localization application may eliminate outlier values of relative distance 480. In addition, the localization application may associate a certainty value or a weight with each region of the triangulated position 470. Accordingly, the determined location of client system 130 may calculated as the sum of the area covered by each region multiplied by the probability that the client system 130 is located in that region. In so doing, if the position of the client system 130 changes and/or the broadcast intensity profile of one or more access points change, the error in determining the true location of the client system 130 may be reduced.

Additionally, or alternatively, the client system 130 may continuously detect broadcast intensities from each access point 360-1, 360-2, or 360-3 and provide associated access point data to the social-networking system 160. However, in some embodiments, the localization application may update the triangulated position 470 only when the triangulated position 470 moves at least a threshold distance. Accordingly, small environmental factors and/or small movements of the client system 130 may not trigger the application to adjust the predicted position of client system 130, while larger signal strength variations due to significant environmental changes or significant movement (e.g., the user carrying the client system to a new location) may trigger the localization application to update the triangulated position 470, This may reduce the computational load placed on the social-networking system 160 and/or the client system 130 and reduce the energy demand associated with determining a location of client system 130 based on the position of local access points 360.

In addition, if client system 130 detects a signal from a new access point 360, the localization application may calculate a relative distance between the new access point 360 and the client system 130. In addition, the client system 130 may further update the triangulated position 470 based upon the new relative distance 480.

FIG. 5 illustrates a peer-to-peer relay of a broadcasted signal from an access point 360. In various embodiments, system environment 500 may include access point 360, first device 510, client system 130, broadcast signal 530, and communication link 540.

In some embodiments, a first device 510 may detect a broadcasted signal 530 from access point 360. The first device 510 may relay the broadcasted signal 530 to a client system 130, via communication link 540. The communication link 540 may operate via peer-to-peer transfer, wireless signals, IR signals, microwave signals, uplink-downlink pairs, and so forth. In so doing, a first device 510 may coordinate the transfer of a broadcasted signal 530 between one or more access points 360 and the client system 130.

In one embodiment, the client system 130 may only track a location of a threshold number of access points 360. Accordingly, a first device 510 extends the functionality of the client system 130 by tracking additional access points and relaying access point data to the client system 130 and/or to the social-networking system 160.

In a second use case, one or more access points 360 may emit an encoded access point ID. The first device 510 may decode the access point ID and/or other access point data, transfer the access point data to client system 130 via communication link 540, and transfer the access point data to social-networking system 160.

Additionally, or alternatively, one or more access points may not be associated with a node on social graph 200. Accordingly, the first device 510 may generate access point data that includes, for example, but without limitation, an access point ID, an access point location, an access point frequency, an access point radial intensity profile, a directionality of the broadcasted signal, and so forth. The first device 510 may further access social graph 200 and generate a node associated with the detected access point. The generated access point data is also stored with the node generated by the first device 510. In addition, the first device 510 may transmit some or all of the access point data to client system 130 via communicative link 540.

Furthermore, in some embodiments, an access point ID associated with access point 360 may change periodically, randomly, and/or pseudo randomly. The first device 510 may determine that an access point 360 is outputting a changed access point ID. The first device 510 may further associate the changed access point ID with the original access point ID in the social graph 200. Additionally, the first device 510 may inform the client system 130 about the change of access point ID with respect to access point 360. For example, the first device 510 may transmit the original access point ID and the changed access point ID to the client system 130. In addition, the first device 510 may transmit instructions to the client system 130 to associate the original ID and/or the changed ID.

In one embodiment, the first device 510 may be a mobile phone running an Android operating system, while the client device 130 may be a mobile phone running iOS.

FIG. 6 illustrates client system 130 receiving location updates based on a location of client system 130 and user data. In particular, system environment 600 may include client system 130, client system location 650, region 610, target destination 620, and location update 625. In various embodiments, as described above, client system 130 detects a location of one or more access points within a broadcast range of client system 130. In various embodiments, the localization application receives access point data from client system 130 and determines a client system location 650 based on the access point data.

In various embodiments, the localization application may provide location-relevant data to a user via client system 130. In particular, a data store 164 may store an indexed list of regions corresponding to a map. Each region may include one or more target destinations, such as a building, a restaurant, a movie theatre, a bar, a scenic park, and so forth. The localization application may search through one or more regions to identify target destinations for which a user has an affinity. For example, in system environment 600, a region 610 may include a target destination 620. In addition, the localization application could determine that a user has an affinity for the target destination 620.

In particular, the localization application may construct a list of prioritized regions. A region may be denoted a prioritized region if a user has a threshold affinity for target destinations included in the region. For example, in system environment 600, if a user has a strong affinity for a target destination 620, then the region 610 may be included in a list of prioritized regions. Additionally, if a user has a moderate affinity for two or more target destinations included in a second region, then the second region may also be included in the list of prioritized regions. However, if a user has low or no affinity for any target destinations in a region, then the region may not be included in the prioritized list of regions. A threshold affinity may be determined based on user data, such as an average or median affinity for regions within a map area.

In various embodiments, prioritized regions may further be ranked based on a degree of user affinity for each prioritized region. Any ranking convention is within the scope of this disclosure, including, but not limited to, numerical rankings (1 thru 10, 1 thru 100, etc.) and non-numerical ranks (e.g., low, medium, high). In addition, the prioritized regions may be ranked based on a proximity of the prioritized region to the client system location 650. For example, a prioritized region that is spatially proximate to client system location 650 may rank higher than a prioritized region that is spatially removed from client system location 650.

In one or more embodiments, the localization application may output the prioritized list of regions to the client system 130 for display to a user. In addition, the localization application may further generate a location update for one or more target destinations for each of one or more high-ranked prioritized regions. For example, localization application may generate and output location update 625 for display on client system 130. In particular, each location update 625 may include, for example, and not by way of limitation, a title of target destination 620, a location of target destination 620, a link to navigation application with direction to target destination 620, one or more advertisements associated with target destination 620, a user affinity rating of target destination 620, a user experience rating of target destination 620, a ranking of region 610 that contains target destination 620, and so forth.

In various embodiments, the localization application may determine a user affinity for a target destination 620 based on user data, such as social signals and/or non-social signals. In particular, the localization application may access social graph 200 to determine if a user has an affinity for a target destination 620 based on one or more social signals, including, but not limited to, a user's location and/or activities during a particular time of day, a day of the week, a weekend or set of days in a month, a season of a year, and/or any time interval during which a target destination 620 may be open and/or available. In addition, the localization application could access social graph 200 to obtain one or more geographic habits of a user, such as one or more regions 610 that a user has visited, to determine if a user has an affinity for a region 610. For example, the localization application could determine that a user has visited a region 610 during a particular time of day, a day of a week, and/or a season of a year to determine that a user has a seasonal affinity for a region 610 and/or a target destination 620. In addition, the localization application could access the social graph 200 to determine that a user has an affinity for a particular location, such as a bar, a restaurant, a store, and so forth (e.g., by evaluating edges in the social graph that connect a node associated with the user to one or more concept nodes).

Furthermore, the localization application may analyze a user's internet usage (e.g., a user's Facebook profile information) to determine that a user has an affinity for a region 610 and/or a target destination 620. For example, the localization application may evaluate Facebook events that a user has viewed, registered for, and/or has “liked” to determine that a user has an affinity for one or more regions 610 and/or target destinations 620 associated with the Facebook event. In addition, the localization application may determine that a user has an affinity for a region if the user performs a social media check-in (e.g., a Facebook check-in) within the region 610. Similarly, the localization application may determine that a user has an affinity for a target destination 620 if the user performs a social media check-in and/or a threshold number of social media check-ins within or nearby target destination 620.

In addition to social signals, the localization application may evaluate one or more non-social signals associated with the user to determine that a user has an affinity for a target destination 620 and/or a region 610. For example, the localization application may evaluate check-ins for flights, check-ins for hotel reservations, location information on a user's calendar, location-related text in a user's short messaging service (SMS) messages and emails, as well as location related data stored in various applications, including, but not limited to, voice/speech-recognition applications and third party applications, such as Uber and Lyft rides to determine that a user has an affinity for a target destination 620 and/or a region 610. In particular, if the localization application determines that a user traveled within region 610 a threshold number of times within a particular time interval, then the localization application could include the region 610 in a prioritized list of regions. Additionally, or alternatively, the localization application could include a region 610 in a prioritized list of regions if the user uses a location-related word associated with a region 610 a certain threshold number of times.

In various embodiments, the localization application may train a machine learning model using user data stored in one or more nodes associated with a user to determine user affinity for one or more target destinations and/or regions. The machine learning model may be user-specific or user-agnostic. Additionally, or alternatively, the localization application may implement a first machine learning model for a first set of users with shared characteristics and may implement a second machine learning model for a second set of users with a different set of shared characteristics. Shared characteristics may be based on information on a user's Facebook profile, demographic information, and so forth.

In various embodiments, the localization application may rank regions included in the prioritized list of regions based on a relative intensity of a user's affinity for a particular region. For example, the localization application may rank a region based on a number of instances that target destinations within a region appear in user data, the number of unique of target destinations within a given region that appear in user data, a degree of directness with which a user references target destinations within a region, a degree of affinity that a user expresses to target destinations within a region, a degree of intentionality that a user expresses to visit a target destination within a region, and a proximity of the region to the client system location 650.

FIG. 7 illustrates a system environment 700, in which the client system 130 is non-stationary. In particular, system environment 700 includes region 710, location update 715, target destination 718, region 720, location update 725, target destination 728, and client system location 730, and client system 130.

As described above, in various embodiments, the localization application may output location updates to the client system 130 for display. The location updates may correspond to one or more target destinations for which a user may have an affinity. In particular, the localization application may access user data stored in relevant nodes of a social graph 200 to characterize a user's affinity profile. Based on the user's affinity profile, the localization application may generate a set of prioritized regions, where each prioritized region includes at least one target destination for which a user has an affinity. The localization application may output to the client system 130 for display the set of prioritized regions, as well as location updates corresponding to one or more of the prioritized regions.

With respect to system environment 700, region 710 and region 720 may comprise a set of prioritized regions. Furthermore, region 710 includes target destination 718 and region 720 includes target destination 728. Based on analyzing user data, the localization application may determine that a user has an affinity for target destination 718 and target destination 728. The localization application may further produce a location update 715 associated with target destination 718 and a location update 725 associated with target destination 728. The localization application further outputs location update 715 and location update 725 for display. As described above, a location update may include, for example, and not by way of limitation, a distance between client system location 730 and a target destination 718, an option to download directions to a target destination 718 via a link to a mapping/navigation application, an advertisement associated with target destination 718, a status/state of target destination 718, and so forth.

In some embodiments, the localization application may periodically, randomly, and/or pseudo-randomly update the client system location 730 based on detected broadcast signals from access points located within a broadcast distance of client system 130 and/or one or more devices that are communicatively linked to client system 130. For example, the localization application may update the client system location 730 once per hundred milliseconds, once per second, once per 10 seconds, once per 30 seconds, once per minute, and so forth.

Additionally, or alternatively, the localization application may vary the frequency at which the client system location 730 is updated. For example, if, after a threshold number of location calculations and/or threshold time interval, the client system 130 has moved less than a threshold distance, then the localization application may decrease the frequency of location calculations. However, if within the threshold number of location calculations and/or threshold time interval, the client system 130 has moved move than a threshold distance, then the localization application may increase the frequency of location calculations. Alternatively, if the mobile device moves approximately a threshold distance during a threshold number of location calculations and/or a threshold time interval, then the localization application may not adjust the frequency of location calculations.

In further embodiments, the localization application may analyze social signals and/or non-social signals to determine a state, activity, and/or behavior of the user. For example, the localization application could determine, based on analyzing user data, that the user is driving on a freeway. Accordingly, the localization application may decrease a frequency of location calculations. Additionally, or alternatively, the localization application may further analyze user data to determine a freeway exit that the user is likely to take. The localization application could access the social graph 200 to determine one or more target destinations proximate to the freeway exit for which the user has an affinity. The localization application could further generate a location update, update a set of prioritized regions to include one or more regions that contain at least part of the target destination, and output the location update and the updated set of prioritized regions for display on client system 130.

Similarly, the localization application may analyze social and non-social signals in user data to determine that a user is taking public transportation (e.g., a train). The localization application could connect to the Internet to download a train schedule for the appropriate train line (e.g., a northbound CalTrain schedule). The localization application could further analyze user data to determine one or more stops at which a user is likely to exit the train. The localization application could further determine one or more target destinations at each of the one or more stops for which a user has an affinity in addition to identifying regions that include at least part of each target destination. In addition, the application could rank the regions based upon a degree of affinity that a user has for the target destination included in the region. The localization application could also generate location updates for each target destination. Furthermore, the localization application could output the target destination and the set of prioritized regions for display on the client system 130.

For example, as shown in system environment 700, a client system 130 may be moving along a train line (e.g., a northbound CalTrain line). The localization application may periodically calculate a client system location 730 of client system 130. The localization application may analyze user data, such as social signals and non-social signals, to determine that the user is likely to exit the train at target destination 718 and/or target destination 728. Accordingly, the localization application may generate location updates for each of target destination 718 and target destination 728. The localization application may further generate a set of prioritized regions 710 and 720. In some embodiments, the localization application may output both location updates for both target destination 718 and target destination 728 for display. In other embodiment, the localization application may first output location update 715 associated with target destination 718 for display. The localization application may further analyze user data to determine if the user is likely to navigate towards target destination 718. For example, the localization application may analyze whether a user viewed location update 715, whether a user selected an advertisement associated with the location update 715, whether the user accesses map applications to find directions to the target destination 718, in addition to other social and non-social signals.

If the application determines that a user is not likely to travel to target destination 718, the localization application may determine another target destination in region 710 for which the user may have an affinity, generate a location update for the new target destination, and output the location update for display. However, if the localization application determines that the user is not likely to exit the train within region 710, the localization application may output location update 725 for display. In particular, location update 725 is associated with region 728 and target destination 720. The localization application may continue analyzing user data to determine if the user is likely to navigate to target destination 728. Accordingly, the localization application may dynamically update location updates based upon user data and client system location 730 to provide a user of client system 130 with relevant location updates.

FIG. 8 illustrates an example method 800 for dynamic location update delivery. The method may begin at step 810, where the localization application receives a first location from client system 130. The first location may be generated based on GPS signals detected by GPS sensors integrated into client system 130. In various embodiments, one or more objects (e.g., building 340) may obstruct GPS sensors from receiving GPS signals, thereby reducing the accuracy of GPS geolocation performed by the client system 130.

At step 820, the localization application receives an access point ID. In various embodiments, the client system 130 may detect one or more broadcasted signals from access points 360 located within a broadcast range of the client system 130. The client system 130 may detect an access point ID associated with the access point 360 and further transmit the access point ID to the social-networking system 160 which executes the localization application.

At step 830, the localization application may identify a second location stored in an index and associated with the access point ID. In particular, the social graph 200 is an index of nodes storing node data and relationships between nodes, referred to as edges. The localization application may search through nodes of a social graph 200 to identify a concept node 204 corresponding to the detected access point 360. In various embodiments, the concept node 204 stores the location of the access point 360, referred to as the second location.

At step 840, the localization application determines a refined location based on the first location and the second location. For example, the localization application could take an average of the first location and the second location to determine a refined location of client system 130. Additionally, or alternatively, the method 800 may return to step 820, where the localization application receives another access point ID corresponding to a second access point 360. The method may continue to step 830, where the localization module obtains a location of the second access point 360 from the social graph 200. At step 840, the localization module could further calculate the refined location by triangulating the location of the client system 130 based on the location of the first access point 360 and the second access point 360.

At step 850, the localization application generates a list of prioritized regions based on the refined location. In particular, the localization application may include a region 610 in a list of prioritized regions based on a user's affinity for the region 610 and the proximity of the region 610 to the refined location. At step 860, the localization application outputs one or more location updates for display on client system 130. In various embodiments, the location updates correspond to target destinations that intersect, or are proximate to, at least one region included in the list of prioritized regions.

In some embodiments, the method 800 continues to step 810, where the localization application receives a first location detected by GPS geolocation performed by the client system 130. In additional embodiments, the method 800 continues to step 820, where the localization application receives an access point ID associated with a broadcasted signal from an access point detected by the client system 130.

Particular embodiments may repeat one or more steps of the method of FIG. 8, where appropriate. Although this disclosure describes and illustrates particular steps of the method of FIG. 8 as occurring in a particular order, this disclosure contemplates any suitable steps of the method of FIG. 8 occurring in any suitable order. Moreover, although this disclosure describes and illustrates an example method for dynamic location update delivery including the particular steps of the method of FIG. 8, this disclosure contemplates any suitable method for dynamic location update delivery including any suitable steps, which may include all, some, or none of the steps of the method of FIG. 8, where appropriate. Furthermore, although this disclosure describes and illustrates particular components, devices, or systems carrying out particular steps of the method of FIG. 8, this disclosure contemplates any suitable combination of any suitable components, devices, or systems carrying out any suitable steps of the method of FIG. 8.

In particular embodiments, one or more objects (e.g., content or other types of objects) of a computing system may be associated with one or more privacy settings. The one or more objects may be stored on or otherwise associated with any suitable computing system or application, such as, for example, a social-networking system 160, a client system 130, a third-party system 170, a social-networking application, a messaging application, a photo-sharing application, or any other suitable computing system or application. Although the examples discussed herein are in the context of an online social network, these privacy settings may be applied to any other suitable computing system. Privacy settings (or “access settings”) for an object may be stored in any suitable manner, such as, for example, in association with the object, in an index on an authorization server, in another suitable manner, or any suitable combination thereof. A privacy setting for an object may specify how the object (or particular information associated with the object) can be accessed, stored, or otherwise used (e.g., viewed, shared, modified, copied, executed, surfaced, or identified) within the online social network. When privacy settings for an object allow a particular user or other entity to access that object, the object may be described as being “visible” with respect to that user or other entity. As an example and not by way of limitation, a user of the online social network may specify privacy settings for a user-profile page that identify a set of users that may access work-experience information on the user-profile page, thus excluding other users from accessing that information.

In particular embodiments, privacy settings for an object may specify a “blocked list” of users or other entities that should not be allowed to access certain information associated with the object. In particular embodiments, the blocked list may include third-party entities. The blocked list may specify one or more users or entities for which an object is not visible. As an example and not by way of limitation, a user may specify a set of users who may not access photo albums associated with the user, thus excluding those users from accessing the photo albums (while also possibly allowing certain users not within the specified set of users to access the photo albums). In particular embodiments, privacy settings may be associated with particular social-graph elements. Privacy settings of a social-graph element, such as a node or an edge, may specify how the social-graph element, information associated with the social-graph element, or objects associated with the social-graph element can be accessed using the online social network. As an example and not by way of limitation, a particular concept node 204 corresponding to a particular photo may have a privacy setting specifying that the photo may be accessed only by users tagged in the photo and friends of the users tagged in the photo. In particular embodiments, privacy settings may allow users to opt in to or opt out of having their content, information, or actions stored/logged by the social-networking system 160 or shared with other systems (e.g., a third-party system 170). Although this disclosure describes using particular privacy settings in a particular manner, this disclosure contemplates using any suitable privacy settings in any suitable manner.

In particular embodiments, privacy settings may be based on one or more nodes or edges of a social graph 200. A privacy setting may be specified for one or more edges 206 or edge-types of the social graph 200, or with respect to one or more nodes 202, 204 or node-types of the social graph 200. The privacy settings applied to a particular edge 206 connecting two nodes may control whether the relationship between the two entities corresponding to the nodes is visible to other users of the online social network. Similarly, the privacy settings applied to a particular node may control whether the user or concept corresponding to the node is visible to other users of the online social network. As an example and not by way of limitation, a first user may share an object to the social-networking system 160. The object may be associated with a concept node 204 connected to a user node 202 of the first user by an edge 206. The first user may specify privacy settings that apply to a particular edge 206 connecting to the concept node 204 of the object, or may specify privacy settings that apply to all edges 206 connecting to the concept node 204. As another example and not by way of limitation, the first user may share a set of objects of a particular object-type (e.g., a set of images). The first user may specify privacy settings with respect to all objects associated with the first user of that particular object-type as having a particular privacy setting (e.g., specifying that all images posted by the first user are visible only to friends of the first user and/or users tagged in the images).

In particular embodiments, the social-networking system 160 may present a “privacy wizard” (e.g., within a webpage, a module, one or more dialog boxes, or any other suitable interface) to the first user to assist the first user in specifying one or more privacy settings. The privacy wizard may display instructions, suitable privacy-related information, current privacy settings, one or more input fields for accepting one or more inputs from the first user specifying a change or confirmation of privacy settings, or any suitable combination thereof. In particular embodiments, the social-networking system 160 may offer a “dashboard” functionality to the first user that may display, to the first user, current privacy settings of the first user. The dashboard functionality may be displayed to the first user at any appropriate time (e.g., following an input from the first user summoning the dashboard functionality, following the occurrence of a particular event or trigger action). The dashboard functionality may allow the first user to modify one or more of the first user's current privacy settings at any time, in any suitable manner (e.g., redirecting the first user to the privacy wizard).

Privacy settings associated with an object may specify any suitable granularity of permitted access or denial of access. As an example and not by way of limitation, access or denial of access may be specified for particular users (e.g., only me, my roommates, my boss), users within a particular degree-of-separation (e.g., friends, friends-of-friends), user groups (e.g., the gaming club, my family), user networks (e.g., employees of particular employers, students or alumni of particular university), all users (“public”), no users (“private”), users of third-party systems 170, particular applications (e.g., third-party applications, external websites), other suitable entities, or any suitable combination thereof. Although this disclosure describes particular granularities of permitted access or denial of access, this disclosure contemplates any suitable granularities of permitted access or denial of access.

In particular embodiments, one or more servers 162 may be authorization/privacy servers for enforcing privacy settings. In response to a request from a user (or other entity) for a particular object stored in a data store 164, the social-networking system 160 may send a request to the data store 164 for the object. The request may identify the user associated with the request and the object may be sent only to the user (or a client system 130 of the user) if the authorization server determines that the user is authorized to access the object based on the privacy settings associated with the object. If the requesting user is not authorized to access the object, the authorization server may prevent the requested object from being retrieved from the data store 164 or may prevent the requested object from being sent to the user. In the search-query context, an object may be provided as a search result only if the querying user is authorized to access the object, e.g., if the privacy settings for the object allow it to be surfaced to, discovered by, or otherwise visible to the querying user. In particular embodiments, an object may represent content that is visible to a user through a newsfeed of the user. As an example and not by way of limitation, one or more objects may be visible to a user's “Trending” page. In particular embodiments, an object may correspond to a particular user. The object may be content associated with the particular user, or may be the particular user's account or information stored on the social-networking system 160, or other computing system. As an example and not by way of limitation, a first user may view one or more second users of an online social network through a “People You May Know” function of the online social network, or by viewing a list of friends of the first user. As an example and not by way of limitation, a first user may specify that they do not wish to see objects associated with a particular second user in their newsfeed or friends list. If the privacy settings for the object do not allow it to be surfaced to, discovered by, or visible to the user, the object may be excluded from the search results. Although this disclosure describes enforcing privacy settings in a particular manner, this disclosure contemplates enforcing privacy settings in any suitable manner.

In particular embodiments, different objects of the same type associated with a user may have different privacy settings. Different types of objects associated with a user may have different types of privacy settings. As an example and not by way of limitation, a first user may specify that the first user's status updates are public, but any images shared by the first user are visible only to the first user's friends on the online social network. As another example and not by way of limitation, a user may specify different privacy settings for different types of entities, such as individual users, friends-of-friends, followers, user groups, or corporate entities. As another example and not by way of limitation, a first user may specify a group of users that may view videos posted by the first user, while keeping the videos from being visible to the first user's employer. In particular embodiments, different privacy settings may be provided for different user groups or user demographics. As an example and not by way of limitation, a first user may specify that other users who attend the same university as the first user may view the first user's pictures, but that other users who are family members of the first user may not view those same pictures.

In particular embodiments, the social-networking system 160 may provide one or more default privacy settings for each object of a particular object-type. A privacy setting for an object that is set to a default may be changed by a user associated with that object. As an example and not by way of limitation, all images posted by a first user may have a default privacy setting of being visible only to friends of the first user and, for a particular image, the first user may change the privacy setting for the image to be visible to friends and friends-of-friends.

In particular embodiments, privacy settings may allow a first user to specify (e.g., by opting out, by not opting in) whether the social-networking system 160 may receive, collect, log, or store particular objects or information associated with the user for any purpose. In particular embodiments, privacy settings may allow the first user to specify whether particular applications or processes may access, store, or use particular objects or information associated with the user. The privacy settings may allow the first user to opt in or opt out of having objects or information accessed, stored, or used by specific applications or processes. The social-networking system 160 may access such information in order to provide a particular function or service to the first user, without the social-networking system 160 having access to that information for any other purposes. Before accessing, storing, or using such objects or information, the social-networking system 160 may prompt the user to provide privacy settings specifying which applications or processes, if any, may access, store, or use the object or information prior to allowing any such action. As an example and not by way of limitation, a first user may transmit a message to a second user via an application related to the online social network (e.g., a messaging app), and may specify privacy settings that such messages should not be stored by the social-networking system 160.

In particular embodiments, a user may specify whether particular types of objects or information associated with the first user may be accessed, stored, or used by the social-networking system 160. As an example and not by way of limitation, the first user may specify that images sent by the first user through the social-networking system 160 may not be stored by the social-networking system 160. As another example and not by way of limitation, a first user may specify that messages sent from the first user to a particular second user may not be stored by the social-networking system 160. As yet another example and not by way of limitation, a first user may specify that all objects sent via a particular application may be saved by the social-networking system 160.

In particular embodiments, privacy settings may allow a first user to specify whether particular objects or information associated with the first user may be accessed from particular client systems 130 or third-party systems 170. The privacy settings may allow the first user to opt in or opt out of having objects or information accessed from a particular device (e.g., the phone book on a user's smart phone), from a particular application (e.g., a messaging app), or from a particular system (e.g., an email server). The social-networking system 160 may provide default privacy settings with respect to each device, system, or application, and/or the first user may be prompted to specify a particular privacy setting for each context. As an example and not by way of limitation, the first user may utilize a location-services feature of the social-networking system 160 to provide recommendations for restaurants or other places in proximity to the user. The first user's default privacy settings may specify that the social-networking system 160 may use location information provided from a client device 130 of the first user to provide the location-based services, but that the social-networking system 160 may not store the location information of the first user or provide it to any third-party system 170. The first user may then update the privacy settings to allow location information to be used by a third-party image-sharing application in order to geo-tag photos.

In particular embodiments, privacy settings may allow a user to specify whether mood or sentiment information associated with the user may be determined, and whether particular applications or processes may access, store, or use such information. The privacy settings may allow users to opt in or opt out of having mood or sentiment information accessed, stored, or used by specific applications or processes. The social-networking system 160 may predict or determine a mood or sentiment associated with a user based on, for example, inputs provided by the user and interactions with particular objects, such as pages or content viewed by the user, posts or other content uploaded by the user, and interactions with other content of the online social network. In particular embodiments, the social-networking system 160 may use a user's previous activities and calculated moods or sentiments to determine a present mood or sentiment. A user who wishes to enable this functionality may indicate in their privacy settings that they opt in to the social-networking system 160 receiving the inputs necessary to determine the mood or sentiment. As an example and not by way of limitation, the social-networking system 160 may determine that a default privacy setting is to not receive any information necessary for determining mood or sentiment until there is an express indication from a user that the social-networking system 160 may do so. By contrast, if a user does not opt in to the social-networking system 160 receiving these inputs (or affirmatively opts out of the social-networking system 160 receiving these inputs), the social-networking system 160 may be prevented from receiving, collecting, logging, or storing these inputs or any information associated with these inputs. In particular embodiments, the social-networking system 160 may use the predicted mood or sentiment to provide recommendations or advertisements to the user. In particular embodiments, if a user desires to make use of this function for specific purposes or applications, additional privacy settings may be specified by the user to opt in to using the mood or sentiment information for the specific purposes or applications. As an example and not by way of limitation, the social-networking system 160 may use the user's mood or sentiment to provide newsfeed items, pages, friends, or advertisements to a user. The user may specify in their privacy settings that the social-networking system 160 may determine the user's mood or sentiment. The user may then be asked to provide additional privacy settings to indicate the purposes for which the user's mood or sentiment may be used. The user may indicate that the social-networking system 160 may use his or her mood or sentiment to provide newsfeed content and recommend pages, but not for recommending friends or advertisements. The social-networking system 160 may then only provide newsfeed content or pages based on user mood or sentiment, and may not use that information for any other purpose, even if not expressly prohibited by the privacy settings.

In particular embodiments, privacy settings may allow a user to engage in the ephemeral sharing of objects on the online social network. Ephemeral sharing refers to the sharing of objects (e.g., posts, photos) or information for a finite period of time. Access or denial of access to the objects or information may be specified by time or date. As an example and not by way of limitation, a user may specify that a particular image uploaded by the user is visible to the user's friends for the next week, after which time the image may no longer be accessible to other users. As another example and not by way of limitation, a company may post content related to a product release ahead of the official launch, and specify that the content may not be visible to other users until after the product launch.

In particular embodiments, for particular objects or information having privacy settings specifying that they are ephemeral, the social-networking system 160 may be restricted in its access, storage, or use of the objects or information. The social-networking system 160 may temporarily access, store, or use these particular objects or information in order to facilitate particular actions of a user associated with the objects or information, and may subsequently delete the objects or information, as specified by the respective privacy settings. As an example and not by way of limitation, a first user may transmit a message to a second user, and the social-networking system 160 may temporarily store the message in a data store 164 until the second user has viewed or downloaded the message, at which point the social-networking system 160 may delete the message from the data store 164. As another example and not by way of limitation, continuing with the prior example, the message may be stored for a specified period of time (e.g., 2 weeks), after which point the social-networking system 160 may delete the message from the data store 164.

In particular embodiments, privacy settings may allow a user to specify one or more geographic locations from which objects can be accessed. Access or denial of access to the objects may depend on the geographic location of a user who is attempting to access the objects. As an example and not by way of limitation, a user may share an object and specify that only users in the same city may access or view the object. As another example and not by way of limitation, a first user may share an object and specify that the object is visible to second users only while the first user is in a particular location. If the first user leaves the particular location, the object may no longer be visible to the second users. As another example and not by way of limitation, a first user may specify that an object is visible only to second users within a threshold distance from the first user. If the first user subsequently changes location, the original second users with access to the object may lose access, while a new group of second users may gain access as they come within the threshold distance of the first user.

In particular embodiments, the social-networking system 160 may have functionalities that may use, as inputs, personal or biometric information of a user for user-authentication or experience-personalization purposes. A user may opt to make use of these functionalities to enhance their experience on the online social network. As an example and not by way of limitation, a user may provide personal or biometric information to the social-networking system 160. The user's privacy settings may specify that such information may be used only for particular processes, such as authentication, and further specify that such information may not be shared with any third-party system 170 or used for other processes or applications associated with the social-networking system 160. As another example and not by way of limitation, the social-networking system 160 may provide a functionality for a user to provide voice-print recordings to the online social network. As an example and not by way of limitation, if a user wishes to utilize this function of the online social network, the user may provide a voice recording of his or her own voice to provide a status update on the online social network. The recording of the voice-input may be compared to a voice print of the user to determine what words were spoken by the user. The user's privacy setting may specify that such voice recording may be used only for voice-input purposes (e.g., to authenticate the user, to send voice messages, to improve voice recognition in order to use voice-operated features of the online social network), and further specify that such voice recording may not be shared with any third-party system 170 or used by other processes or applications associated with the social-networking system 160. As another example and not by way of limitation, the social-networking system 160 may provide a functionality for a user to provide a reference image (e.g., a facial profile, a retinal scan) to the online social network. The online social network may compare the reference image against a later-received image input (e.g., to authenticate the user, to tag the user in photos). The user's privacy setting may specify that such voice recording may be used only for a limited purpose (e.g., authentication, tagging the user in photos), and further specify that such voice recording may not be shared with any third-party system 170 or used by other processes or applications associated with the social-networking system 160.

In particular embodiments, changes to privacy settings may take effect retroactively, affecting the visibility of objects and content shared prior to the change. As an example and not by way of limitation, a first user may share a first image and specify that the first image is to be public to all other users. At a later time, the first user may specify that any images shared by the first user should be made visible only to a first user group. The social-networking system 160 may determine that this privacy setting also applies to the first image and make the first image visible only to the first user group. In particular embodiments, the change in privacy settings may take effect only going forward. Continuing the example above, if the first user changes privacy settings and then shares a second image, the second image may be visible only to the first user group, but the first image may remain visible to all users. In particular embodiments, in response to a user action to change a privacy setting, the social-networking system 160 may further prompt the user to indicate whether the user wants to apply the changes to the privacy setting retroactively. In particular embodiments, a user change to privacy settings may be a one-off change specific to one object. In particular embodiments, a user change to privacy may be a global change for all objects associated with the user.

In particular embodiments, the social-networking system 160 may determine that a first user may want to change one or more privacy settings in response to a trigger action associated with the first user. The trigger action may be any suitable action on the online social network. As an example and not by way of limitation, a trigger action may be a change in the relationship between a first and second user of the online social network (e.g., “un-friending” a user, changing the relationship status between the users). In particular embodiments, upon determining that a trigger action has occurred, the social-networking system 160 may prompt the first user to change the privacy settings regarding the visibility of objects associated with the first user. The prompt may redirect the first user to a workflow process for editing privacy settings with respect to one or more entities associated with the trigger action. The privacy settings associated with the first user may be changed only in response to an explicit input from the first user, and may not be changed without the approval of the first user. As an example and not by way of limitation, the workflow process may include providing the first user with the current privacy settings with respect to the second user or to a group of users (e.g., un-tagging the first user or second user from particular objects, changing the visibility of particular objects with respect to the second user or group of users), and receiving an indication from the first user to change the privacy settings based on any of the methods described herein, or to keep the existing privacy settings.

In particular embodiments, a user may need to provide verification of a privacy setting before allowing the user to perform particular actions on the online social network, or to provide verification before changing a particular privacy setting. When performing particular actions or changing a particular privacy setting, a prompt may be presented to the user to remind the user of his or her current privacy settings and to ask the user to verify the privacy settings with respect to the particular action. Furthermore, a user may need to provide confirmation, double-confirmation, authentication, or other suitable types of verification before proceeding with the particular action, and the action may not be complete until such verification is provided. As an example and not by way of limitation, a user's default privacy settings may indicate that a person's relationship status is visible to all users (i.e., “public”). However, if the user changes his or her relationship status, the social-networking system 160 may determine that such action may be sensitive and may prompt the user to confirm that his or her relationship status should remain public before proceeding. As another example and not by way of limitation, a user's privacy settings may specify that the user's posts are visible only to friends of the user. However, if the user changes the privacy setting for his or her posts to being public, the social-networking system 160 may prompt the user with a reminder of the user's current privacy settings of posts being visible only to friends, and a warning that this change will make all of the user's past posts visible to the public. The user may then be required to provide a second verification, input authentication credentials, or provide other types of verification before proceeding with the change in privacy settings. In particular embodiments, a user may need to provide verification of a privacy setting on a periodic basis. A prompt or reminder may be periodically sent to the user based either on time elapsed or a number of user actions. As an example and not by way of limitation, the social-networking system 160 may send a reminder to the user to confirm his or her privacy settings every six months or after every ten photo posts. In particular embodiments, privacy settings may also allow users to control access to the objects or information on a per-request basis. As an example and not by way of limitation, the social-networking system 160 may notify the user whenever a third-party system 170 attempts to access information associated with the user, and require the user to provide verification that access should be allowed before proceeding.

FIG. 9 illustrates an example computer system 900. In particular embodiments, one or more computer systems 900 perform one or more steps of one or more methods described or illustrated herein. In particular embodiments, one or more computer systems 900 provide functionality described or illustrated herein. In particular embodiments, software running on one or more computer systems 900 performs one or more steps of one or more methods described or illustrated herein or provides functionality described or illustrated herein. Particular embodiments include one or more portions of one or more computer systems 900. Herein, reference to a computer system may encompass a computing device, and vice versa, where appropriate. Moreover, reference to a computer system may encompass one or more computer systems, where appropriate.

This disclosure contemplates any suitable number of computer systems 900. This disclosure contemplates computer system 900 taking any suitable physical form. As example and not by way of limitation, computer system 900 may be an embedded computer system, a system-on-chip (SOC), a single-board computer system (SBC) (such as, for example, a computer-on-module (COM) or system-on-module (SOM)), a desktop computer system, a laptop or notebook computer system, an interactive kiosk, a mainframe, a mesh of computer systems, a mobile telephone, a personal digital assistant (PDA), a server, a tablet computer system, an augmented/virtual reality device, or a combination of two or more of these. Where appropriate, computer system 900 may include one or more computer systems 900; be unitary or distributed; span multiple locations; span multiple machines; span multiple data centers; or reside in a cloud, which may include one or more cloud components in one or more networks. Where appropriate, one or more computer systems 900 may perform without substantial spatial or temporal limitation one or more steps of one or more methods described or illustrated herein. As an example and not by way of limitation, one or more computer systems 900 may perform in real time or in batch mode one or more steps of one or more methods described or illustrated herein. One or more computer systems 900 may perform at different times or at different locations one or more steps of one or more methods described or illustrated herein, where appropriate.

In particular embodiments, computer system 900 includes a processor 902, memory 904, storage 906, an input/output (I/O) interface 908, a communication interface 910, and a bus 912. Although this disclosure describes and illustrates a particular computer system having a particular number of particular components in a particular arrangement, this disclosure contemplates any suitable computer system having any suitable number of any suitable components in any suitable arrangement.

In particular embodiments, processor 902 includes hardware for executing instructions, such as those making up a computer program. As an example and not by way of limitation, to execute instructions, processor 902 may retrieve (or fetch) the instructions from an internal register, an internal cache, memory 904, or storage 906; decode and execute them; and then write one or more results to an internal register, an internal cache, memory 904, or storage 906. In particular embodiments, processor 902 may include one or more internal caches for data, instructions, or addresses. This disclosure contemplates processor 902 including any suitable number of any suitable internal caches, where appropriate. As an example and not by way of limitation, processor 902 may include one or more instruction caches, one or more data caches, and one or more translation lookaside buffers (TLBs). Instructions in the instruction caches may be copies of instructions in memory 904 or storage 906, and the instruction caches may speed up retrieval of those instructions by processor 902. Data in the data caches may be copies of data in memory 904 or storage 906 for instructions executing at processor 902 to operate on; the results of previous instructions executed at processor 902 for access by subsequent instructions executing at processor 902 or for writing to memory 904 or storage 906; or other suitable data. The data caches may speed up read or write operations by processor 902. The TLBs may speed up virtual-address translation for processor 902. In particular embodiments, processor 902 may include one or more internal registers for data, instructions, or addresses. This disclosure contemplates processor 902 including any suitable number of any suitable internal registers, where appropriate. Where appropriate, processor 902 may include one or more arithmetic logic units (ALUs); be a multi-core processor; or include one or more processors 902. Although this disclosure describes and illustrates a particular processor, this disclosure contemplates any suitable processor.

In particular embodiments, memory 904 includes main memory for storing instructions for processor 902 to execute or data for processor 902 to operate on. As an example and not by way of limitation, computer system 900 may load instructions from storage 906 or another source (such as, for example, another computer system 900) to memory 904. Processor 902 may then load the instructions from memory 904 to an internal register or internal cache. To execute the instructions, processor 902 may retrieve the instructions from the internal register or internal cache and decode them. During or after execution of the instructions, processor 902 may write one or more results (which may be intermediate or final results) to the internal register or internal cache. Processor 902 may then write one or more of those results to memory 904. In particular embodiments, processor 902 executes only instructions in one or more internal registers or internal caches or in memory 904 (as opposed to storage 906 or elsewhere) and operates only on data in one or more internal registers or internal caches or in memory 904 (as opposed to storage 906 or elsewhere). One or more memory buses (which may each include an address bus and a data bus) may couple processor 902 to memory 904. Bus 912 may include one or more memory buses, as described below. In particular embodiments, one or more memory management units (MMUs) reside between processor 902 and memory 904 and facilitate accesses to memory 904 requested by processor 902. In particular embodiments, memory 904 includes random access memory (RAM). This RAM may be volatile memory, where appropriate. Where appropriate, this RAM may be dynamic RAM (DRAM) or static RAM (SRAM). Moreover, where appropriate, this RAM may be single-ported or multi-ported RAM. This disclosure contemplates any suitable RAM. Memory 904 may include one or more memories 904, where appropriate. Although this disclosure describes and illustrates particular memory, this disclosure contemplates any suitable memory.

In particular embodiments, storage 906 includes mass storage for data or instructions. As an example and not by way of limitation, storage 906 may include a hard disk drive (HDD), a floppy disk drive, flash memory, an optical disc, a magneto-optical disc, magnetic tape, or a Universal Serial Bus (USB) drive or a combination of two or more of these. Storage 906 may include removable or non-removable (or fixed) media, where appropriate. Storage 906 may be internal or external to computer system 900, where appropriate. In particular embodiments, storage 906 is non-volatile, solid-state memory. In particular embodiments, storage 906 includes read-only memory (ROM). Where appropriate, this ROM may be mask-programmed ROM, programmable ROM (PROM), erasable PROM (EPROM), electrically erasable PROM (EEPROM), electrically alterable ROM (EAROM), or flash memory or a combination of two or more of these. This disclosure contemplates mass storage 906 taking any suitable physical form. Storage 906 may include one or more storage control units facilitating communication between processor 902 and storage 906, where appropriate. Where appropriate, storage 906 may include one or more storages 906. Although this disclosure describes and illustrates particular storage, this disclosure contemplates any suitable storage.

In particular embodiments, I/O interface 908 includes hardware, software, or both, providing one or more interfaces for communication between computer system 900 and one or more I/O devices. Computer system 900 may include one or more of these I/O devices, where appropriate. One or more of these I/O devices may enable communication between a person and computer system 900. As an example and not by way of limitation, an I/O device may include a keyboard, keypad, microphone, monitor, mouse, printer, scanner, speaker, still camera, stylus, tablet, touch screen, trackball, video camera, another suitable I/O device or a combination of two or more of these. An I/O device may include one or more sensors. This disclosure contemplates any suitable I/O devices and any suitable I/O interfaces 908 for them. Where appropriate, I/O interface 908 may include one or more device or software drivers enabling processor 902 to drive one or more of these I/O devices. I/O interface 908 may include one or more I/O interfaces 908, where appropriate. Although this disclosure describes and illustrates a particular I/O interface, this disclosure contemplates any suitable I/O interface.

In particular embodiments, communication interface 910 includes hardware, software, or both providing one or more interfaces for communication (such as, for example, packet-based communication) between computer system 900 and one or more other computer systems 900 or one or more networks. As an example and not by way of limitation, communication interface 910 may include a network interface controller (NIC) or network adapter for communicating with an Ethernet or other wire-based network or a wireless NIC (WNIC) or wireless adapter for communicating with a wireless network, such as a WI-FI network. This disclosure contemplates any suitable network and any suitable communication interface 910 for it. As an example and not by way of limitation, computer system 900 may communicate with an ad hoc network, a personal area network (PAN), a local area network (LAN), a wide area network (WAN), a metropolitan area network (MAN), or one or more portions of the Internet or a combination of two or more of these. One or more portions of one or more of these networks may be wired or wireless. As an example, computer system 900 may communicate with a wireless PAN (WPAN) (such as, for example, a BLUETOOTH WPAN), a WI-FI network, a WI-MAX network, a cellular telephone network (such as, for example, a Global System for Mobile Communications (GSM) network), or other suitable wireless network or a combination of two or more of these. Computer system 900 may include any suitable communication interface 910 for any of these networks, where appropriate. Communication interface 910 may include one or more communication interfaces 910, where appropriate. Although this disclosure describes and illustrates a particular communication interface, this disclosure contemplates any suitable communication interface.

In particular embodiments, bus 912 includes hardware, software, or both coupling components of computer system 900 to each other. As an example and not by way of limitation, bus 912 may include an Accelerated Graphics Port (AGP) or other graphics bus, an Enhanced Industry Standard Architecture (EISA) bus, a front-side bus (FSB), a HYPERTRANSPORT (HT) interconnect, an Industry Standard Architecture (ISA) bus, an INFINIBAND interconnect, a low-pin-count (LPC) bus, a memory bus, a Micro Channel Architecture (MCA) bus, a Peripheral Component Interconnect (PCI) bus, a PCI-Express (PCIe) bus, a serial advanced technology attachment (SATA) bus, a Video Electronics Standards Association local (VLB) bus, or another suitable bus or a combination of two or more of these. Bus 912 may include one or more buses 912, where appropriate. Although this disclosure describes and illustrates a particular bus, this disclosure contemplates any suitable bus or interconnect.

Herein, a computer-readable non-transitory storage medium or media may include one or more semiconductor-based or other integrated circuits (ICs) (such, as for example, field-programmable gate arrays (FPGAs) or application-specific ICs (ASICs)), hard disk drives (HDDs), hybrid hard drives (HHDs), optical discs, optical disc drives (ODDs), magneto-optical discs, magneto-optical drives, floppy diskettes, floppy disk drives (FDDs), magnetic tapes, solid-state drives (SSDs), RAM-drives, SECURE DIGITAL cards or drives, any other suitable computer-readable non-transitory storage media, or any suitable combination of two or more of these, where appropriate. A computer-readable non-transitory storage medium may be volatile, non-volatile, or a combination of volatile and non-volatile, where appropriate.

Herein, “or” is inclusive and not exclusive, unless expressly indicated otherwise or indicated otherwise by context. Therefore, herein, “A or B” means “A, B, or both,” unless expressly indicated otherwise or indicated otherwise by context. Moreover, “and” is both joint and several, unless expressly indicated otherwise or indicated otherwise by context. Therefore, herein, “A and B” means “A and B, jointly or severally,” unless expressly indicated otherwise or indicated otherwise by context.

The scope of this disclosure encompasses all changes, substitutions, variations, alterations, and modifications to the example embodiments described or illustrated herein that a person having ordinary skill in the art would comprehend. The scope of this disclosure is not limited to the example embodiments described or illustrated herein. Moreover, although this disclosure describes and illustrates respective embodiments herein as including particular components, elements, feature, functions, operations, or steps, any of these embodiments may include any combination or permutation of any of the components, elements, features, functions, operations, or steps described or illustrated anywhere herein that a person having ordinary skill in the art would comprehend. Furthermore, reference in the appended claims to an apparatus or system or a component of an apparatus or system being adapted to, arranged to, capable of, configured to, enabled to, operable to, or operative to perform a particular function encompasses that apparatus, system, component, whether or not it or that particular function is activated, turned on, or unlocked, as long as that apparatus, system, or component is so adapted, arranged, capable, configured, enabled, operable, or operative. Additionally, although this disclosure describes or illustrates particular embodiments as providing particular advantages, particular embodiments may provide none, some, or all of these advantages. 

What is claimed is:
 1. A method, comprising, by one or more computing devices: receiving, from a client system of a user, a first location of the client system; receiving, from the client system, an ID of a first access point detected by the client system; accessing an index to determine a second location of the first access point based on the ID; determining a refined location of the client system based on the first location and the second location; generating a prioritized list of regions based on the refined location and user data; and transmitting information associated with the prioritized list of regions to the client system.
 2. The method of claim 1, further comprising: associating the ID of the first access point with at least one region of a map; calculating a distance between the at least one region and the refined location; determining that the calculated distance is within a distance threshold; and adding the at least one region to the prioritized list of regions.
 3. The method of claim 1, further comprising: receiving two or more IDs associated with other access points, wherein each other access point is detected by the client system; accessing the index to determine a map coordinate for each detected other access point; and updating the refined location of the client system by triangulating the map coordinates of the detected other access points.
 4. The method of claim 3, further comprising receiving a signal strength associated with each detected other access point and updating the refined location based on the signal strength of each detected other access point.
 5. The method of claim 4, wherein the client system is configured to detect signals broadcasted over at least one of Wi-Fi®, Bluetooth®, radio frequency, near field communications, or infrared wireless communication protocols.
 6. The method of claim 1, wherein generating the prioritized list of regions further comprises: determining a target destination that is associated with the user; selecting a first region that includes the target destination; and adding the first region to the prioritized list of regions.
 7. The method of claim 6, wherein generating the prioritized list of regions further comprises: determining that a second region is associated with the user; and adding the second region to the prioritized list of regions, wherein the second region is associated with the user: when a user-generated location is confirmed to be within the second region; when the refined location of the client system is within the second location; or when the client system is periodically located in the second location.
 8. The method of claim 1, wherein the user data includes at least one of social signals and non-social signals, wherein the social signals and the non-social signals are included in a social graph.
 9. The method of claim 8, wherein the social signals include one or more of the following: a time interval during which a target destination associated with a node of the social graph is accessible to the user; a first node of the social graph for which the user has an affinity to; and social media check-ins corresponding to a second node of the social graph.
 10. The method of claim 8, wherein the non-social signals comprise one or more of third-party location tracking applications, location-related text in emails and Short Messaging Service messages, location-related reservations on calendar applications, and travel-related check-ins.
 11. The method of claim 1, further comprising, upon receiving a location ping from the client system, updating the prioritized list of regions.
 12. The method of claim 1, further comprising modifying a frequency at which location pings are requested from the client system based upon on or more of the current location of the client system, a time of day, a user activity associated in a social graph with the time of day, and a velocity at which the client system is moving.
 13. The method of claim 1, further comprising: detecting a direction in which the client system is moving; and updating the prioritized list of regions based on the direction.
 14. The method of claim 9, wherein the target destination corresponds to a concept node in the social graph, wherein each concept node is associated with at least one region in a map.
 15. The method of claim 8, wherein generating the prioritized list of regions further comprises: adding a first region to the prioritized list of regions based on a number of the social signals and the non-social signals associated with the first region; and determining a rank of the first region based on the number of social signals and the non-social signals associated with the first region.
 16. The method of claim 1, further comprising: determining that the client system is located proximate to a second access point located within a building; and triggering the client device to detect a first signal strength from a third access point located proximate to the second access point.
 17. The method of claim 16, further comprising: receiving a social graph with a map coordinate of a fourth access point located proximate to the second access point; prompting the client system to detect a second signal strength of the fourth access point; and triangulating the first signal strength of the third access point and the second signal strength of the fourth access point to calculate the refined location of the client system.
 18. The method of claim 1, wherein the information associated with a target destination transmitted to the client system includes one or more of: an advertisement associated with the target destination, a survey to rate user experience of an entity at the target destination, and a recommendation about goods and services offered at the target destination.
 19. One or more non-transitory, computer-readable storage media embodying software that is operable when executed to: receive, from a client system of a user, a first location of the client system; receive, from the client system, an ID of a first access point detected by the client system; access an index to determine a second location of the first access point based on the ID; determine a refined location of the client system based on the first location and the second location; generate a prioritized list of regions based on the refined location and user data; and transmit information associated with the prioritized list of regions to the client system.
 20. A system comprising: a client system of a user; one or more processors; and a memory coupled to the processors comprising instructions executable by the processors, the processors being operable when executing the instructions to: receive, from the client system, a first location of the client system; receive, from the client system, an ID of a first access point detected by the client system; access an index to determine a second location of the first access point based on the ID; determine a refined location of the client system based on the first location and the second location; generate a prioritized list of regions based on the first location and user data; and transmit information associated with the prioritized list of regions to the client system. 